Interactive networking systems with user classes

ABSTRACT

A networking system may comprise a web site incorporating a combination of one or more of the following: a crediting system, a chat bidding system, a performance bidding system, a telephony switching system, a media interaction system, a display system, a photo management system, and a messaging system. The networking system may categorize each user of the web site into classes, including a featured class, a common class, a sponsored class, and a sponsoring class. The networking system may facilitate user interactions, some of which may be partially dependent on user classes. A featured user may opt to temporarily appear as a common user, thus activating an alternative user profile and hiding his featured status. A sponsored user may participate in interactions on the web site if a sponsoring user offers his credits to pay for the sponsored member&#39;s participation. Other aspects of the networking system are also disclosed herein.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 12/237,316, filed 24 Sep. 2008, which claims priority and thebenefit, under 35 U.S.C. §119(e), of both U.S. Provisional PatentApplication 60/974,723, filed 24 Sep. 2007, and U.S. Provisional PatentApplication 61/059,444, filed 6 Jun. 2008. This application is also acontinuation-in-part of U.S. patent application Ser. No. 12/709,205,filed 19 Feb. 2010. The disclosures of all four of these priorityapplications are hereby incorporated by reference as if fully set forthbelow.

BACKGROUND

1. Technical Field

Various aspect of the present invention relate to social andprofessional networking and, more particularly, to interactivenetworking systems for enabling interaction between users belonging toone or more classes.

2. Description of Related Art

Conventional social and professional networking systems enable users tointeract with one another via various networking protocols. Thesesystems provide a variety of services, but they generally lack theability to classify a user's network of contacts to provide varyinglevels of communication capabilities among different levels of users.

Such conventional systems are also not designed for serving as social orprofessional networking and communications platforms where certainindividuals are highly sought after communication partners. For example,while celebrities are able to register and utilize conventionalnetworking systems to communicate directly with their friends andacquaintances, celebrities do not currently have the ability toselectively allow communications from their fans.

These conventional systems are also generally limited in how they allowvarious users to communicate with one another. For example, conventionalsystems generally limit inter-user communications to chat rooms, messageboards, and/or private email messages.

Therefore, there is a need in the art for a system that providesincreased communications capabilities.

There is also a need for a networking system whereby users can controlcommunication capabilities pertaining to communications with otherusers, where such controls may be at least partially based on a class ofsuch users.

There is a further need for such a networking system having safetycontrols enabling member interactions while allowing a receiving partyto establish criteria controlling receipt of communications.

There is a further need for such a networking system, in whichcelebrities may communicate directly with fans in a virtual environmentproviding real-time interaction.

It is to such a networking system that that the present invention isdirected.

SUMMARY

Exemplary embodiments of the present invention may include interactivenetworking systems providing various communication features. Embodimentsmay allow multiple user classes. In an exemplary embodiment, thenetworking system may comprise any or all of various components,including a classification system, a crediting system, a chat biddingsystem, a performance bidding system, a telephony switching system, amedia interaction system, a display system, a photo management system,and a messaging system.

To enable operation of such components of the networking system, thenetworking system may additionally comprise a server assembly. Theserver assembly may comprise one or more web servers for hosting the website. A user may interact with the web site through a web client adaptedto display the web site. The web client may receive requests from theuser and direct such requests to the server assembly. The serverassembly may call various operations or programs to implement componentsand operations of the web site. The server assembly may send responsesto user requests through the web client to the user.

The classification system may categorize each user into one or moreclasses, and may dynamically update the class of each user as needed.For example, and not limitation, the networking system may include afeatured class, a common or regular class, a sponsored class, asponsoring class, or a combination of these classes. The featured classmay include users who are deemed desirable contacts for other users. Forexample, celebrities subscribed to the networking system may be membersof the featured class. The sponsored class may include users whoseactivities associated with the networking system are paid for by one ormore other users. The sponsoring class may include sponsors of thoseincluded in the sponsored class. The common class may include users whoare not featured users or, in some embodiments, users who belong to noother class.

The classification system may associate each user account with one ormore classes to which the corresponding user belongs. In someembodiments, the classification system may temporarily or permanentlychange a user's classes as needed. A first user who is a featured user,for example, may request a temporary switch from the featured class tothe common class. The classification system may then automatically anddynamically update the web site to indicate that the first user is amember of the common class, without the featured user having to log outand log back into a different account. While the first user istemporarily treated as a common user, a representation of the first userviewed by another user may be a particular representation used for thecommon class. Accordingly, the featured user may essentially hide his orher featured status on demand.

The crediting system may manage credit associated with the useraccounts. Each user of the web site may have, or be associated with, auser account for accessing the web site.

According to the crediting system of the networking system, each useraccount may be associated with a credit account for purchasing servicesfrom the web site. The credit account may represent virtual funds foruse on the web site. When a first user's credit account is less than orequal to a predetermined threshold, such as zero, the first user mayautomatically become a member of the sponsored class. Other members maythen opt to use their own credits for interactions with the sponsoredfirst user in situations where the first user would otherwise have theoption of using his or her own credits.

The chat bidding system, if included, may enable common users to posetasks to a featured user in an organized manner. The chat bidding systemmay generally comprise a featured user, a plurality of common users, anda tasks queue.

The featured user may represent a person or entity in which the commonusers have interest. For example, the featured user may be a celebrity,a doctor, a counselor, or the like. The featured user may use a featureduser account to interact with the web site.

The common users may have an interest in the featured user. For example,the common users may be fans of the featured user. Through the chatbidding system, the common users may pose tasks to the featured user. Acommon user may pledge credits for a task, thereby associating the taskwith a bid value. The amount of the bid value may be debited from theuser's credit account.

The tasks queue may comprise hardware, software, or a combinationthereof, in communication with the server assembly. The tasks queue mayorganize the tasks in an order corresponding to the bids associated withthe tasks.

Through a web client in communication with the server assembly, thefeatured user may be presented with the tasks in an order determined bythe tasks queue and, therefore, determined by the bids associated withthe tasks. For each presented task, the featured user may dispatch thetask by responding to or skipping the task.

If included, the performance bidding system may enable users to performon the web site in an organized manner. The performance bidding systemmay comprise a plurality of users and a performance queue.

Each user may request an opportunity to perform, and may associate suchrequest with a bid. The bid value may represent a number of creditsdeducted from the user's account in return for the user's performance.

The performance queue may comprise hardware, software, or a combinationthereof, in communication with the server assembly. The performancequeue may organize the performance requests in an order corresponding tothe bids associated with the requests. A user may be allowed to performon the web site when the user's request reaches a top of the queue.

If included in the web site, the telephony switching system may enableanonymous contact between two parties having user accounts on the website. The telephony switching system may generally comprise a firstcommunication device, a second communication device, a service center,and a telephony switch.

The first communication device and second communication device may beregistered with the service center, and such registration may occur overthe web site. Each registration may include a set of contact rulesspecifying who may connect to the applicable communication device, andwhen such connections may occur.

A first user associated with the first communication device may requesta connection to a second user associated with the second communicationdevice. The service center may receive the request and, based on thecontact rules, may determine whether the requested connection isallowed.

The telephony switch may be in communication with the service center. Ifthe requested connection is allowed, the service center may forward theconnection request to the telephony switch. In turn, the telephonyswitch may connect the first communication device to the secondcommunication device. Accordingly, the two communication devices may beconnected to each other without phone numbers of either communicationdevice being shared with the other communication device.

If included in the web site, the media interaction system may enable afirst user to interact with a second user by extending a media object tothe second user. The media object may be customizable, and may comprisevarious media, including animations, audio, or text. The media objectmay overlay other objects displayed on a client computer of the firstuser and a client computer of the second user.

If included, a display system may enable color and theme changes of theweb site as viewed by a web client. Based on a user request, a colorscheme and theme of the web site may be altered in response to a userrequest.

The photo management system, if included in the web site, may enableusers of the web site to manage and edit digital images stored on theserver assembly. The photo management system may comprise an imagelibrary and an image editor. The image library may contain imagesselected or created by a particular user, and the image editor mayenable the user to edit images in the image library.

Additionally, a messaging system, if included, may enable a first userto leave a message on a virtual message board of a second user. Themessaging system may comprise a message area, one or more graphicaltools, and a color selector. The first user may select a graphical tooland a color, and may then modify an image of the message area in amanner customizable based on the chosen graphical tool and color.

These and other objects, features, and advantages of the interactivenetworking system will become more apparent upon reading the followingspecification in conjunction with the accompanying drawing figures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A illustrates an architecture of a client computer utilizing aninteractive networking system, in accordance with an exemplaryembodiment of the present invention.

FIG. 1B illustrates an architecture of a server assembly of thenetworking system, according to an exemplary embodiment of the presentinvention.

FIG. 2 illustrates a map diagram of user classes in the networkingsystem, according to an exemplary embodiment of the present invention.

FIG. 3 illustrates a block diagram of the networking system, accordingto an exemplary embodiment of the present invention.

FIG. 4 illustrates a web page of the networking system, incorporating aplurality of customizable action cards, according to an exemplaryembodiment of the present invention.

FIG. 5A illustrates a customizable action card representation of a userof the networking system, according to an exemplary embodiment of thepresent invention.

FIG. 5B illustrates a user interface for customizing action cards of thenetworking system, according to an exemplary embodiment of the presentinvention.

FIG. 6 illustrates a block diagram of a chat bidding system of thenetworking system, according to an exemplary embodiment of the presentinvention.

FIG. 7 illustrates a flow diagram of an operation of the chat biddingsystem of the networking system, according to an exemplary embodiment ofthe present invention.

FIG. 8 illustrates a flow diagram of a process of a featured userinitiating and participating in a chat bidding session of the chatbidding system, according to an exemplary embodiment of the presentinvention.

FIGS. 9A-9B illustrate flow diagrams of a process of the featured usermoderating the chat bidding session of the chat bidding system,according to an exemplary embodiment of the present invention.

FIG. 10 illustrates a flow diagram of a process of a common user joiningthe chat bidding session of the chat bidding system, according to anexemplary embodiment of the present invention.

FIG. 11 illustrates a flow diagram of a process of the userparticipating in the chat bidding session of the chat bidding system,according to an exemplary embodiment of the present invention.

FIG. 12 illustrates a flow diagram of an operation of a performancebidding system of the networking system, according to an exemplaryembodiment of the present invention.

FIG. 13A illustrates a process of registering a communication devicewith the telephony switching system of the networking system, accordingto an exemplary embodiment of the present invention.

FIGS. 13B-13C illustrate block diagrams of a telephony switching systemof the networking system, according to an exemplary embodiment of thepresent invention.

FIG. 14 illustrates a flow diagram of a method of handling a connectionrequest from a calling party to a receiving party in the telephonyswitching system of the networking system, according to an exemplaryembodiment of the present invention.

FIG. 15 illustrates a flow diagram of an operation of a mediainteraction system of the networking system, according to an exemplaryembodiment of the present invention.

FIG. 16 illustrates a flow diagram of an operation of a photo managementsystem of the networking system, according to an exemplary embodiment ofthe present invention.

FIG. 17 illustrates a flow diagram of an operation of a photo editor ofthe photo management system of the networking system, according to anexemplary embodiment of the present invention.

FIG. 18 illustrates a flow diagram of an implementation of the photoeditor of the photo management system, according to an exemplaryembodiment of the present invention.

FIG. 19 illustrates a flow diagram of a process of displaying an imagein the photo management system of the networking system, according to anexemplary embodiment of the present invention.

FIG. 20 illustrates a web page of a messaging system of the networkingsystem, according to an exemplary embodiment of the present invention.

FIG. 21 illustrates a flow diagram of an operation of leaving a messagethrough a messaging system of the networking system, according to anexemplary embodiment of the present invention.

FIG. 22 illustrates a flow diagram of an operation of retrievingmessages from the messaging system of the networking system, accordingto an exemplary embodiment of the present invention.

FIG. 23 illustrates a flow diagram of a general operation of themessaging system of the networking system, according to an exemplaryembodiment of the present invention.

DETAILED DESCRIPTION

To facilitate an understanding of the principles and features of theinvention, various illustrative embodiments are explained below. Inparticular, the invention is described in the context of being aweb-based interactive networking system for celebrities and their fans.Embodiments of the invention, however, are not limited to web-basedimplementations, or to use by celebrities and fans. Rather, embodimentsof the invention may be used for networking and interaction betweenvarious entities and individuals in various environments, particularlywhen the use of multiple user classes would be beneficial. For example,and not limitation, doctors, counselors, sports figures, and politiciansmay benefit from the embodiments of the invention.

Throughout the present description, the present invention is describedas embodied in a web environment. However, those of skill in the artwill recognize that the concepts of the invention are not limited to aweb environment and could be applied to various other systems.Accordingly, reference to web components is for convenience, and suchreferences should not be considered limiting.

For example, and not limitation, embodiments of the present networkingsystem may be implemented in media centers, video game consoles,operating systems, and virtual machines. Media centers may includetelevision, telephone, and internet technologies, any of which mayutilize various embodiments of the present networking system. Further,video game consoles now implement social networking, internetcommunications, video recording, and digital file downloading.Interactive networking may be useful in such video consoles, and may beprovided by embodiments of the present networking system. Operatingsystems, such as Linux™, Mac OS X™, and Microsoft Windows™, enablecertain technologies to be implemented within the operating systemoutside of the framework of the World Wide Web. Accordingly, embodimentsof the networking system may be utilized in such operating systemswithout use of the World Wide Web. In addition, technologies such asJava™ and Adobe Air™ allow functionality outside the scope of the WorldWide Web, in the context of “virtual machines,” which may utilize thepresent networking system.

Exemplary embodiments of the networking system may contain componentsthat may be utilized in a wide variety of applications. Some exemplaryembodiments may be for personal entertainment, and others may be forprofessional use. Professional uses of the networking system mayinclude, without limitation, medical personnel recruiting, educationalapplications, and various other applications matching persons topersons, persons to services, or persons to products. The networkingsystem may comprise various classes of users, and may enable one or moreuser classes to control access and duration of interaction betweenthemselves and users of one or more other user classes.

The components described hereinafter as making up various elements ofthe invention are intended to be illustrative and not restrictive. Manysuitable components that would perform the same or similar functions ascomponents described herein are intended to be embraced within the scopeof the invention. Such other components not described herein mayinclude, but are not limited to, for example, components developed afterdevelopment of the invention.

Various embodiments of the present invention comprise interactivenetworking systems.

Referring now to the figures, wherein like reference numerals representlike parts throughout the views, various embodiments of the networkingsystem will be described in detail.

FIG. 1A illustrates a computer architecture for a client computer 102,in accordance with an exemplary embodiment of the present invention. Theclient computer 102 may be used to access the networking system 300,including a web site 305 provided by the networking system 300 (See FIG.3). Those skilled in the art will recognize that the generalarchitecture described with reference to FIG. 1A is for example only,and may be modified to accommodate various embodiments of the networkingsystem and particular operational environments.

As shown in FIG. 1A, the client computer 102 may comprise a centralprocessing unit 105 (“CPU”) and one or more system memories 107, such asa random access memory 109 (“RAM”) and a non-volatile memory, such as aread-only memory (“ROM”) 111. The client computer 102 may furthercomprise a system bus 112 coupling together the memory 107, the CPU 5,and various other components. A basic input/output system containingroutines to assist in transferring information between components of theclient computer 102 may be stored in the ROM 111. Additionally, theclient computer 102 may include a mass storage device 114 for storing anoperating system 116, application programs, and other program modules.

The mass storage device 114 is generally connected to the CPU 105through a mass storage controller (not shown) connected to the bus 112.The mass storage device 114 and its associated computer-readable mediaprovide non-volatile storage for the client computer 102. Although thedescription of computer-readable media contained herein generally refersto a mass storage device, such as a hard disk or CD-ROM drive, it willbe appreciated by those skilled in the art that computer-readable mediamay include any available media accessible by the client computer 102 ora server assembly 150 (FIG. 1B).

By way of example, and not limitation, the computer-readable media maycomprise computer storage media and communication media. Computerstorage media may include volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EPROM, EEPROM, flash memory, other solid statememory technology, CD-ROM, digital versatile disks (“DVD”), otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage, other magnetic storage devices, or any other media that may beused to store the desired data and may be accessible by the clientcomputer 102 or the server assembly 150. Computer-readable instructionson the storage media of the client computer 102 may include, forexample, instructions for implementing processes, preferably client-sideprocesses, of the networking system 300.

According to various embodiments, the client computer 102 may operate ina networked environment using logical connections to remote computers,such as the server assembly 150, through a network 118, such as theInternet. The client computer 102 may connect to the network 118 througha network interface unit 120 connected to the bus 112. It will beappreciated that the network interface unit 120 may also be utilized toconnect to other types of networks and remote computer systems.

The client computer 102 may also include an input/output controller 122for receiving and processing input from a number of other devices,including a keyboard, mouse, or electronic stylus. The input/outputcontroller 122 may provide output to a display screen, a printer, orother type of output device.

A number of program modules and data files may be stored in the massstorage device 114 and RAM 109 of the client computer 102. Such programmodules and data files may include an operating system 116 suitable forcontrolling operations of a networked personal computer. A web browserapplication program, or web client 124, may also be stored on the massstorage device 114 and the RAM 109. The web client 124 may comprise anapplication program for requesting and rendering web pages 126 createdin Hypertext Markup Language (“HTML”) or other types of markuplanguages. The web client 124 may also be capable of executing scriptsthrough the use of a scripting host. The scripting host executes programcode expressed as scripts within the browser environment.

The web client 124 may be operative to execute one or more client sideobjects. As discussed briefly above, client side objects are executableobjects that may be identified in a web page 126 and executed inconjunction with the rendering of the web page 126. For instance, Java™applets or ActiveX™ controls may be identified on a web page 126 andrendered by the web client 124 to generate a portion of the web page 126display.

According to an exemplary embodiment of the invention, the web client124 may be further operative to utilize client side objects called webpart objects 128A-128C, or web parts. Web part objects 128A-128C arereusable client side objects that stand and contain web-based contentsuch as Extensible Markup Language (“XML”), HTML, and scripts. Web parts128A-128C have a set of standard properties that control how they arerendered. These properties enable web parts to be storage-neutral andreusable. Because web parts 128A-128C adhere to a common standard, theymay be stored in libraries, which may be utilized to create a variety ofweb pages 126. Web pages 126 that include web part objects 128A-128C maybe referred to herein as web part pages.

Referring now to FIG. 1B, a server assembly 150 utilized in variousexemplary embodiments of the networking system 300 (FIG. 3) will bedescribed. The server assembly 150 may service the web site 305 byreceiving and responding to requests from web clients 124. The serverassembly 150 may comprise various combinations of hardware and softwarefor servicing the web site 305. Those skilled in the art will recognizethat the server assembly 150 illustrated in FIG. 1B is an exemplaryserver configuration and may be modified to accommodate variousembodiments of the networking system 300. As shown in FIG. 1B, theserver assembly 150 may include many of the conventional computingcomponents included in the client computer 102 and described above withrespect to FIG. 1A. In particular, the server assembly 150 may include aCPU 105, a network interface unit 120 connected to a network 118, suchas the Internet, a system memory 107, and a mass storage device 114.

The mass storage device 114 utilized by the server assembly 150 maytypically be operative to store an operating system 116 suitable forservicing the web site 305 and controlling operations of a servercomputer. The mass storage device 114 and its associatedcomputer-readable storage media provide non-volatile storage for theserver assembly 150. Computer storage media may include volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information, such ascomputer-readable instructions, data structures, program modules, orother data. Computer-readable instructions on the computer-readablemedia of the server assembly 150 may include, for example, instructionsfor implementing processes, preferably server-side processes, of thenetworking system 300.

The server assembly 150 may utilize a web server application 155. Theweb server application 155 may receive and respond to requests from webclients 124 at remote computers, such as the client computer 102, forweb pages 126 located at or accessible to the server assembly 150. Itwill be appreciated that web pages 126, as described herein, includeboth those pages stored statically and utilizing only HTML, as well aspages generated dynamically through use of server-side scriptingtechnologies.

According to various embodiments of the networking system 300, the webserver application 155 may receive requests for web pages 126 thatinclude one or more web parts 128A-128C. As discussed above, web parts128A-128C comprise client-side objects that may be used by the webclient 124 when displaying a web page 126.

FIG. 3 illustrates a block diagram of the networking system 300,according to an exemplary embodiment of the present invention. Thenetworking system 300 may operate in an environment of the clientcomputer 102 and the server assembly 150. As shown in FIG. 3, anexemplary embodiment of the networking system 300 may comprise aninteractive networking web site 305, the server assembly 150, and a website manager 308. The client computer 102 may interact with the web site305 and, accordingly, the server assembly 150 through the web client 124at the client computer 102.

The web site 305 may enable interaction between and among one or morefeatured users and a plurality of common users. The featured users mayinteract with one another via the web site 305, and similarly, thecommon users may interact with one another via the web site 305.Additionally, the common users may desire some level of interaction withthe featured users, and the featured users may desire some level ofprivacy in their interactions with the common users. For example, afeatured user may be a celebrity, and a set of common users may be fansof the celebrity. The web site 305 may provide a virtual environment forsuch interactions.

The server assembly 150 may service the web site 305. The serverassembly 150 may operate as discussed in detail above, or in variousmanners for providing services to client computers 102 over a network.

The web site manager 308 may manage the web site 305, act asadministrator of the web site 305, and provide customer service to usersof the web site 305. Preferably, the web site manager 308 may be one ormore humans or entities, but may also comprise computing devices andautomated services.

The web site 305 may generally comprise any combination of the followingcomponents: a crediting system 310, a classification system 320, a chatbidding system 330, a performance bidding system 340, a telephonyswitching system 350, a media interaction system 360, a display system370, a photo management system 380, and a messaging system 390. Eachcomponent of the web site 305 may provide various services as describedfurther below.

Crediting System

The web site 305 may include a crediting system 310 to provide users ameans to purchase services of the web site 305. Each user may have auser account, and the user account may be associated with the user'shistory of activities on the web site 305. According to the creditingsystem 310, the user account may include a credit account representingvirtual credits allotted to the user. The credits may be used topurchase services from the web site 305, or products and services fromentities associated with the web site 305.

The web site 305 may provide multiple categories of credits, such asuniversal credits and limited credits. Universal, or non-promotional,credits may be purchasable by the user. The user may purchase universalcredits from the web site manager 308 via the web site 305, over a phonecall, or via various other means of communicating a desire to purchasecredits. In contrast, limited, or promotional, credits may be awarded tothe user based on promotions. The web site 305 may separately accountfor universal and limited credits. However, the web site 305 may presentthe user with either a combined total of credits or with separate totalsfor each of universal and limited credit accounts. As mentioned above,various services of the web site 305 may be purchased with credits.Preferably, predetermined exclusive services of the web site 305 may bepurchased only with universal credits, while non-exclusive services maybe purchased with universal credits, limited credits, or variouscombinations thereof.

As will be discussed in more detail below, the networking system 300 mayprovide various classes of user membership. For example, and notlimitation, the web site 305 may provide featured user accounts forfeatured users and common user accounts for common users. The users maypurchase services, such as participation in web site activities, withtheir credit accounts. Such services may include opportunities tointeract with the featured users. Purchasable services may be activitiesof the chat bidding system 330, the performance bidding system 340, thetelephony switching system 350, the media interaction system 360, thedisplay system 370, the photo management system 380, the messagingsystem 390, and/or other web service systems.

For purchase of services on the web site 305, the web site 305 mayimplement a predetermined scheme for determining which credits aredebited from the purchasing user's credit account. For example, and notlimitation, a purchase of an exclusive service may automatically debitthe user's universal credits. For a purchase of a non-exclusive service,the user may be allowed to specify which credits are debited for thepurchase. Alternatively, the web site 305 may implement afirst-in-first-out accounting, in which the first credits placed intothe user's credit account are the first credits debited from the usersaccount, or a last-in-first-out accounting, in which the last creditsplaced in the user's account are the first credits debited from the useraccount. As another option, the web site 305 may automatically debit anyavailable limited credits before universal credits for the purchase ofnon-exclusive services.

Through the use of credit accounts, common users may interact withfeatured users, and as a result, common users, featured users, and theweb site manager 308 may profit from such interaction. Common users maybenefit by fulfilling desires to interact with featured users, such ascelebrities, who might otherwise be inaccessible to the common users.Featured users may interact with common users and, thereby, increasetheir popularity and fan bases. Further, featured users may haveagreements with the web site manager 308, whereby featured users sharein revenues generated by the web site 305 or whereby the web sitemanager 308 donates revenues from the web site 305 to favored charitiesof the featured users. Additionally, the web site manager 308 may reapfinancial benefits through selling credits to common users.

Classification System

The classification system 320 may classify each user of the networkingsystem 300 into one or more user classes. In an exemplary embodiment,each user is a member of at least one user class, and each user may be amember of multiple user classes. Some user classes may be mutuallyexclusive with other user classes, in which case each user may be amember of no more than one of each such mutually exclusive classes. Notall user classes need be mutually exclusive with one another, however,so a user may be a member of multiple user classes.

FIG. 2 illustrates a map diagram of various classes of the networkingsystem 300, according to an exemplary embodiment of the presentinvention. As shown in FIG. 2, user classes of the networking system 300may include the following, for example: featured class 210, common class220, sponsored class 230, and sponsoring class 240. Other classes may beused instead of, or in addition to, those illustrated in FIG. 2. Forexample, in some embodiments, the networking system 300 may comprise twoor more sub-communities, such as a dating sub-community and a job searchsub-community. Each sub-community to which a user belongs or on which auser is currently active may correspond to a class of that user.Accordingly, a user who is a member of the dating sub-community may bedeemed a member of a dating class.

In addition to any classes defined by the networking system 300, theclassification system 320 may also maintain user-defined classes definedby individual users for their own use. For example, and not limitation,a first user may create a friends class, a family class, or a co-workersclass. That first user may categorize other users of the networkingsystem 300 into the user-defined classes. In some embodiments, the firstuser's classifications of other users may be private, such that otherusers cannot see the first user's user-defined classes or theclassifications of various users.

The featured class 210 may be a class for members who are in high demandfor interactions with other members. For example, celebrities may bemembers of the featured class 210. The common class 220 may comprise allthose members who are not classified as featured members or all thoseusers who are otherwise unclassified. Accordingly, in some exemplaryembodiments of the networking system 300, the featured class 210 and thecommon class 220 may be mutually exclusive, as shown in FIG. 2. Thefeatured class 210 and the common class 220 may also be comprehensive insome embodiments, such that each and every user may belong to one ofthese two classes, as is also shown in FIG. 2.

In some embodiments of the networking system 300, featured users (i.e.,members of the featured class 210) may have access to one or morefeatures or activities of the web site 305 that are unavailable to thecommon users (i.e., members of the common class 220). For example, afeatured user may be allowed to participate in more or differentactivities than common users on the web site 305. For further example,each featured user may have more than a single user profile.

Each user of the networking system 300 may be associated with a profile,and each user's associated user profile may include various informationrelated to the corresponding user. Information included in the user'sprofile may include the following, for example: name; photo or otherselected image; tagline; relationship status; information entered by theuser about himself or herself, such as interests and hobbies;information about the user entered by others; and history of activitieson the web site 305. Each user may also have an associated profile page,which may be a page on the web site 305 that provides or summarizes theinformation in the user's profile. A user may visit another user'sprofile page, for example, to learn more about the other user or toinitiate an interaction with the other user. A common user may have asingle profile and single profile page associated with his common useraccount. As mentioned above, a featured user may have one or more thanone profile associated with a featured user account and, accordingly,may have one or more than one profile page associated with the featureduser account.

A featured user may have two profiles associated with a featured useraccount, a featured profile and an alternative profile. Because the twoprofiles are associated with a single account, the featured user neednot log out and log back in, or otherwise re-authenticate to a secondaccount, to switch between the two profiles. Rather, the networkingsystem 300 may dynamically effect the switch upon request from thefeatured user. The featured and alternative profiles may each containthe same types of information related to the featured user. For example,and not limitation, both the featured and alternative profiles maycomprise a name, history of web site activities within that profile, andphotos. The information in each profile, however, may be distinct fromthe other profile. Accordingly, even though both profiles are associatedwith a single featured user account, a first set of data related to thefeatured user may be associated with the featured profile, while asecond set of data related to the featured user may be associated withthe alternative profile. Each data set corresponding to a specificprofile may comprise its own user name, photos, activity history,friends list, or various other information related to the featured user.

In an exemplary embodiment, a featured user may be a celebrity and mayuse his or her featured profile as a celebrity profile, with which fansmay interact. The alternative profile may be the featured user'snon-celebrity profile, such that switching to the alternative profileenables the celebrity to hide the celebrity status. For example, thefeatured user may opt to interact with only personal friends and familymembers through the alternative profile.

As discussed in more detail below, users may participate in variousactivities on the web site 305 of the networking system 300. In someinstances, the activities available to a particular user or the rolesavailable to the particular user within an activity may vary based onwhether the user is a featured user or not. In some or all of suchactivities, a featured user may play the same or similar role as commonusers when the alternative profile of the featured user is active.Activities and roles within certain activities that are limited tofeatured users may not be accessible to a featured user when thealternative profile is active. Alternatively, when any such activity orrole is accessed by a featured user with an active alternative profile,the networking system 300 may automatically activate the featuredprofile and deactivate the alternative profile, thus enabling thefeatured user to access features of the networking system 300 that arelimited to featured users. In short, the featured user may be treated asa common user and may appear to others on the web site 305 as a commonuser, when the alternative profile is active.

A featured user may switch back and forth between profiles upon requestto the networking system 300. If the featured user indicates to thenetworking system 300 that he or she would like to hide his or herfeatured status, or switch to the alternative profile, then thenetworking system 300 may respond by activating the alternative profile.When the alternative profile for the featured user is active, thenetworking system 300 may dynamically update the web site 305 so thatsome or all other users see the featured user as a common user. In anexemplary embodiment, no more than one of these profiles may be activeat a given time. Thus, when the alternative profile is activated, thefeatured profile may be automatically deactivated. Analogously, when thefeatured profile is activated, the alternative profile may beautomatically deactivated.

Various aspects of the web site 305 of the networking system 300 maydynamically update when a featured user switches profiles. For example,when a featured user switches to her alternative profile, some or allrepresentations of the featured user throughout the web site 305 may bemodified to disguise the featured user as a common or non-featured user,or to falsely indicate that the featured user is a common user. As aresult, the featured user may be attributed common user status in someor all activities in which the featured user participated while thealternative profile remains active. When a featured user switches fromher alternative profile to the featured profile, some or allrepresentations of the featured user on the web site 305 may indicatethat the featured user is indeed a featured user, and the user may thenbe treated fully as a featured user by the web site 305.

In one or more instances, the web site 305 may provide representationsof one or more users, so that a current user viewing the representationsmay learn about or interact with the other users through thoserepresentations. In an exemplary embodiment, a representation may be agraphical object, such as an icon, an identification card, or a profilepage.

In addition to identifying a particular user, a representation of theparticular user may also include one or more characteristics thatidentify one or more classes of the particular user. In an exemplaryembodiment, representations of common users may have a firstcharacteristic not had by representations of those who appear to befeatured users. Representations of featured users with active featuredprofiles may have a second characteristic not had by common users. Afeatured user with an active alternative profile may be provided withthe first characteristic, such that the featured user may appear to be acommon user. For example, and not limitation, the first characteristicmay be a certain color, icon, or template associated with the profilepage or other representation of common users (and featured users withactive alternative profiles). The second characteristic may also be acertain color, icon, or template, or may be simply the lack of the firstcharacteristic. Analogously, the first characteristic may simply be thelack of the second characteristic. Accordingly, the first characteristicmay behave as a class-identifier to users of the web site 305, and mayidentify a featured user as being a non-featured user when the featureduser desires.

In some embodiments, both the alternative profile and the featuredprofile of a featured user may remain visible in some respects on theweb site 305 by other users, regardless of which profile is currentlyactive. For example, although a featured user may be actively using hisor her alternative profile, a profile page associated with the featuredprofile may remain accessible to users of the web site 305. As a result,users may continue to interact with the featured profile, e.g., byleaving messages and requesting to become a fan, even when the featureduser is currently using the alternative profile. Analogously, users withthe proper access may continue to interact with the featured user'salternative profile, while the featured user uses the featured profile.

The sponsored class 230 may comprise all members who have equal or lessthan a sponsorship threshold number of credits in their user account.For example, and not limitation, the sponsorship threshold number ofcredits may be zero, such that a sponsored user has no credits or anegative number of credits in his or her credit account. A sponsoreduser may thus rely on sponsorship to participate in activities of thenetworking system 300 that require payment. In an exemplary embodiment,a user may become a sponsored member automatically when the credits inhis credit account drop to or below the sponsorship threshold.

As will be discussed in more detail below, various users of thenetworking system 300 may participate in various activities, includinginteractions with one another, through the web site 305. In someinstances, an activity may be associated with a cost, such that a useris required to pay credits corresponding to the associated cost toparticipate in the activity. In the case of a sponsored user, however,an associated sponsoring user may pay the credits on the sponsoreduser's behalf.

The sponsoring class 240 may include users who have indicated that theywill or might sponsor a sponsored user. There may be various reasons whya first user may choose to sponsor a second user. For example, and notlimitation, sponsorship may enable the sponsoring user to interact withthe sponsored user through purchasable activities of the web site 305 inwhich the sponsored user may not otherwise be able to participate. Ifthe sponsoring user believes that he or she would benefit from thesponsored user's participation, i.e., by spending time with thesponsored user, then the sponsoring user may sponsor the sponsored userin such activity. Alternatively, a sponsoring user may be an advertiserthat sponsors the sponsored user in exchange for some service providedby the sponsored user, such as reviewing or promoting the sponsoringuser's products or services. Other reasons for sponsorship may alsoexist and may vary between sponsoring users of the networking system300.

In some embodiments of the networking system 300, a first user need nothave a credit balance at or below a sponsorship threshold to be eligiblefor sponsorship. Rather, in some embodiments, no sponsorship thresholdneed be used at all or in all circumstances. For example, and notlimitation, a sponsoring user may opt to pay for the first user'sparticipation in an activity even though the first user has enoughcredits to pay for his or her own participation. For another example, anadvertiser may choose to sponsor a user who has enough credits to payfor his or her own participation in an activity, when that user providesa service to the advertiser in return.

When a user is sponsored despite having a credit balance above asponsorship threshold, the networking system may, or may not, deem thatuser to be a member of the sponsored user class 230, depending on theparticular implementation of the networking system 300. In an exemplaryembodiment, the sponsored user class 230 may be made up of only thoseusers whose credit accounts are at or below the sponsorship threshold.In such an embodiment, these sponsored users' credit balances may be toolow to enable them to sponsor other users, and thus the sponsoring class240 and the sponsored class 230 of users may be mutually exclusive. Somealternative embodiments may include in the sponsored class 230 one ormore users who have enough credits to potentially become sponsorsthemselves. In this case, the sponsored class 230 and the sponsoringclass 240 may overlap, as shown in FIG. 2.

A sponsoring user may specify a particular sponsored user or users tosponsor, or may opt to become a general sponsor whose credit may beavailable by request on a case-by-case basis. In some embodiments, thepairing of a sponsored user with a sponsoring user may be prompted byeither party, and either party may be able to refuse the sponsorship. Insome other embodiments, only a potential sponsoring user may prompt thepairing. A sponsored user may have the option of refusing sponsorship ingeneral or sponsorship of a particular other user. If a sponsorshiprelationship is formed, i.e., if both parties agree to the sponsorshipor if neither party objects, then the sponsored user and the sponsoringuser may be associated with each other in the networking system 300.

In general, a sponsoring party may pay for one or more activities toallow an associated sponsored user to participate in such activities. Insome embodiments of the networking system 300, the sponsoring party onlypays for interactions that involve both the sponsored user and thesponsoring user, and such sponsored interactions may be paid for by thesponsoring user on a case-by-case basis as requested by the sponsoringuser. In other embodiments, the sponsoring user may pay for everyactivity in which the sponsored user opts to participate on the web site305. In still other embodiments, the circumstances in which thesponsoring user pays on behalf of the sponsored user may depend onsponsorship rules that apply to the sponsorship relationship between thetwo parties.

Either party to a sponsorship relationship, i.e., either the sponsoringuser or the sponsored user, may specify sponsorship rules to apply tothe relationship. The sponsorship rules may be guidelines indicating thecircumstances in which the sponsoring user will pay on behalf of thesponsored user. For example, and not limitation, the guidelines mayprovide a schedule during which sponsorship applies; a duration ofsponsorship; a total balance available to the sponsoring user; a set ofactivities to be sponsored; a set of activities to be excluded fromsponsorship; a set of users with whom interactions are sponsored; or aset of users with whom interactions are excluded from sponsorship. Thesponsorship rules may specify automatic payment in some or allinstances, or that the sponsoring party must approve some or allactivities before payment is made. In some embodiments, each sponsoringuser may specify default sponsorship rules to be used for everysponsorship relationship in which he or she is involved. These defaultrules may be modifiable and customizable on a case-by-case basis.

When the networking system 300 receives a request for a sponsored userto participate in an activity that has an associated cost, thenetworking system 300 may determine whether the sponsored user isassociated with a sponsoring user. For each associated sponsoring useridentified, the networking system 300 may then determine whether theapplicable sponsorship rules allow payment for the desired activity. Ifno associated sponsoring user is identified whose sponsorship rulesallow payment, the networking system 300 may refuse to allow thesponsored user's participation in the activity or, alternatively, thenetworking system 300 may send out an alert to other users indicatingthat the sponsored user seeks an immediate sponsor. If a singlesponsoring user is identified whose sponsorship rules allow payment forthe selected activity, then the cost of the activity may be withdrawnfrom that sponsoring user's account to pay for the sponsored user'sparticipation in the activity.

On the other hand, if multiple associated sponsors are identified whosesponsorship rules allow payment for the selected activity, then thenetworking system 300 may apply a predetermined sponsorship formula todetermine which one or more of the sponsoring users pay for theactivity. The sponsorship formula may be a system-defined formula, maybe part of the sponsorship rules, or may be defined by the sponsoreduser. For example, the sponsorship formula may simply select whicheversponsoring user the sponsored user wishes to be billed. For anotherexample, the networking user may arrange the sponsoring users in aranked list and may select the sponsoring user at the top of the list,before then moving that sponsoring user to the bottom of the list forpayment on a later activity. For still another example, the sponsorshipformula may split the cost of the activity equally or in predeterminedweighted proportions among the applicable sponsoring users.

In an exemplary embodiment of the networking system 300, a sponsoreduser need not always have an associated sponsoring user. If this is thecase, then the sponsored user may be unable to participate innon-complimentary activities of the networking system 300 until asponsoring user is found or until enough credits are added to thesponsored user's account to pay for the desired activities.

FIG. 4 illustrates an exemplary web page 400 of the web site 305 of thenetworking system 300, according to an exemplary embodiment of thepresent invention. As mentioned above, a web page 400 of the web site305 may display representations 450 of other users, to enable a currentuser to view information about or interact with other users of the website 305.

A representation 450 of another user may be, for example, a profilepage, an icon or photo, or an identification card. The representation450 may have some characteristic identifying a class of the userrepresented. Representations 450 of common users and featured users(with active featured profiles) may be distinguishable from each otherin some manner, such as by a predetermined characteristic that is commonto users of the same class. For example, as shown in FIG. 4, the commonuser representations 450 a may be a different color than the featureduser representations 450 b. Representations 450 of featured users withactive alternative profiles, however, may share the predeterminedcharacteristic of the representations 450 of common users and maytherefore be indistinguishable from common users in some instances.

The type or appearance of a representation 450 of a particular seconduser as displayed to a current user may depend on various factors,including for example: the particular web page 400 of the web site 305that provides the representation 450, the classes of the second user,and customizations made by the current user. For example, and notlimitation, on a profile page of the second user, the representation 450of the second user that is displayed to the current user may befull-page description of the second user. Alternatively, if the currentuser is browsing some other page 400 of the web site 305, therepresentation 450 of the second user may appear as a small icon,identification card, or other identifier that preferably takes up only asmall portion of the web page 400, such as in FIG. 4.

The representations 450 need not be displayed to the current user at alltimes while the current user uses the networking system 300. Forexample, the representations 450 may be displayed on only the home pageof the current user, or only when the current user navigates to certainweb pages of the networking system 300. Some exemplary embodiments,however, may display the representations 450 on every page of thenetworking web site 305, such as in a stationary frame object 405 of thewebsite 305.

Because the networking system 300 may have numerous users, not everyuser need be represented by the representations 450 displayed to thecurrent user. The subset of representations 450 actually displayed maybe selected by various means. For example, and not limitation, in someembodiments, only “friends” of the current user are represented indisplayed representations 450, or only a random subset of friends isrepresented. Alternatively, only users currently logged in to the website 305 may be represented in the displayed representations 450; arotating selection of all users may be represented in the displayedrepresentations 450; or the current user may preselect which user'srepresentations 450 will be displayed.

FIG. 5A illustrates an exemplary action card 500, which may be used bythe networking system 300 as an interactive representation 450 of auser. The networking system 300 may provide one or more action cards 500as the representations 450 of other users, wherein an action card 500may identify the particular user with whom it is associated and my alsoidentify one or more classes of the associated user, such as either thecommon 220 or featured class 210. When a featured user has an activealternative profile, his or her action card 500 may identify her as acommon user.

As shown in FIG. 5A, an action card 500 may comprise, for example, userinformation 510, a user picture 520, and one, two, or more actionindicators 530. The user information 510 and user picture 520 may beitems for the associated user's profile. In the case of a featured user,the information shown in the corresponding action card 500 or otherrepresentation 450 may be information from the active profile of thefeatured user. As shown, for example, the user information 510 mayinclude the user's username, tagline, age, height, and builddescription. The picture 520 may be a picture 520 selected by thecorresponding user to represent the user in his or her profile.

Each action card 500 may identify the represented user, and may alsoinclude a plurality of placeholders 550. Each placeholder may contain anaction indicator 530, where an action indicator 530 may correspond to anaction that may be performed by the networking system 300 on therepresented user, or between the represented user and the current userinteracting with the action card 500. For example, and not limitation:action indicators 530 may be provided for any or all of the following:email the user; call the user; initiate chat session with the user;invite the user to an activity; and request friendship with the user.When the current user selects an action indicator 530 on an action card500, the networking system 300 may respond by performing the actionindicated by the action indicator 530 and, where appropriate, byperforming that action between the current user and the user representedby the action card 500.

The action cards 500, or other user representations 450, viewable by thecurrent user may be customizable by the current user. For example, thecurrent user may customize the appearance of representations 450, and anaction card 500 may be further customized to contain the actionindicators 530 that the current user finds most useful. The actionindicators 530 shown in the placeholders 550 of an action card 500 mayvary between different action cards 500. The networking system 300 mayprovide one or more representation templates for each user, and thecurrent user may customize each template to specify an appearance ofaction cards 500 based on that template.

In an exemplary embodiment of the networking system 300, the networkingsystem 300 may allow the current user to customize a distinctrepresentation template for each of one or more user classes. A uniquetemplate may be customizable for each of the common and featuredclasses. Analogously, a unique template may be customizable for each ofthe sponsored class and the sponsoring class. A unique template may alsobe customized for each class associated with members of a sub-communityof the networking system 300. When action cards 500 are presented to thecurrent user on the web site 305, the action indicators 530 in eachaction card 500 may correspond to those selected for the user class towhich the user represented by the action card 500 belongs. If thecurrent user utilizes certain operations more in interacting with afirst class of users than with a second class of users, the current usermay opt to customize the action cards 500 of those user classesaccordingly. Accordingly, the current user may not only identify theclasses of other users based on their action cards 500, but may alsointeract with other users as desired through use of the action cards500.

Customizations of representation templates may vary between useraccounts. As a result, an action card 500 for a particular user may havea different appearance and different action indicators 530 when viewedthrough different user accounts.

FIG. 5B illustrates a user interface for customizing action cards of thenetworking system, according to an exemplary embodiment of the presentinvention. As shown in FIG. 5B, the networking system 300 may presentthe user with one or more templates 500 a and 500 b, where each template500 a or 500 b corresponds to action cards 500 for members for acorresponding class of users. Customizations made to a template 500 afor Class A may be applied to action cards 500 representing members ofClass A. Customizations made to a template 500 b for Class B may beapplied to action cards 500 representing members of Class B. Forexample, Class A may be the class of featured users, while Class B isthe class of common users; or Class A may be the class of sponsoredusers, while Class B is the class of sponsoring users. As shown in FIG.5B, action card templates 500 a and 500 b for different classes maydiffer from one another even before customization, such as by beingdifferent colors, having different background images, or having otheridentifiable characteristics. Each action card 500 may inherit thesedistinctions from its corresponding template 500 a or 500 b, such thataction cards 500 may be quickly identifiable as corresponding to usersbelonging to certain classes.

The networking system 300 may provide a plurality of available actionindicators 530. Each action indicator 530 may represent and correspondto an action that the current user may desire to perform. Templates 500a or 500 b and action cards 500 may each have one or more placeholders550, and each placeholder 500 may be filled with an action indicator530. In appearance, an action indicator 530 may be various displayableobjects, such as an icon, an image, or a text string briefly describingthe corresponding action.

In an exemplary embodiment, the action indicators 530 correspond toactions that may connect two or more users in an interaction, such as achat interaction or transmission of a message from one user to another.Action indicators 530 may represent, for example, one or more of thefollowing operations that may be performed by the networking system:block user, add event, view related events, add note, add to contacts,add to favorites, add to taggers, blogs, chat, chat history, customizesounds, view mail history, view media gallery, public group invite, sendvideo mail, send virtual café item, send virtual drink, send virtualgift, SMS notification, sync to contact, watch intro video, join fanclub, media gallery, call, email, write on page, or watch video. In someembodiments, the networking system 300 may also enable users to createtheir own action indicators 530, such as by recording a series of tasksand associating the series with a representative image, icon, text, orother object receivable by a placeholder 550 of an action card 500.

As shown in FIG. 5B, the networking system 300 may present a currentuser with a plurality of available action indicators 530, such as in anaction list 560. The action indicators 530 within the action list 560may change based on which action card template 500 is active andcurrently being customized. In other words, when the current user clickson a first action card template 500 a, the action list 560 may containthe action indicators 530 available for inclusion in that template 500.If the current user then clicks on a second action card template 500 bthat has different action indicators 530 available to it, the actionlist 560 may automatically change to list the action indicators 530 thatare available for inclusion in the second action card template 500.There may be various reasons why an action indicator 530 would beavailable to one action card template 500 a and not available to anotheraction card template 500 b. For example, and not limitation, it may bedesirable to limit interactions with featured users by common users. Tothis end, certain action indicators 530 representing means ofcommunication may be unavailable to a common user for inclusion in anaction card template 500 a or 500 b corresponding to the featured class,so as to limit those means of communication between featured users andcommon users.

The current user may select a subset of the action indicators 530 to beincluded in the placeholders 550 of each action card template 500 a or500 b, where a different subset of action indicators 530 may be selectedfor each action card template 500 a or 500 b. The current user mayselect action indicators 530 for a template 500 by selecting eachdesired action indicator 530 from the action list 560, such as byholding a mouse button down when the mouse cursor hovers over the actionindicator 530, and then dragging the desired action indicator 530 to aplaceholder 550 within the action card template 500. After an actionindicator 530 is moved to a placeholder 550 in a template 500, theaction indicator 530 may remain displayed in that placeholder 550 in theuser-friendly customization interface to remind the current user of hisor her selections. If the current user wishes to remove an actionindicator 530 from a placeholder 550, he or she may simply drag theaction indicator 530 out of the placeholder 550 or may replace theaction indicator 530 with another action indicator 530 by selecting theother action indicator 530, such as by dragging, for the sameplaceholder 550.

After receiving the current user's selections of action indicators 530for one or more templates 500 a and 500 b, the networking system 300 maythen associate the selected subsets with the action card templates 500 aand 500 b for which the subsets were selected. Accordingly, the userclasses corresponding to a particular action card template 500 a or 500b may also be associated with the selected subset of action indicators530. When an action card 500 is displayed to the current user, thataction card's placeholders 550 may hold the action indicators 530selected by the current user for the applicable action card template 500a or 500 b. Accordingly, a class of a user may be identified by theaction card 500 used to represent that user.

Because user classes may overlap, a user may belong to multiple classes,such as the common class and the sponsored class. In some embodiments ofthe networking system 300, multiple classes of a user may be indicatedin some manner on the representation 450, such as an action card 500, ofthat user. In some other embodiments, if a user falls into multipleclasses, then that user's representation 450 may be determined based onthe user's priority class. The networking system 300 may provide aformula for determining the user's priority class and correspondingrepresentation template. The priority formula may be system-defined ordefined by the current user for use within the current user's account.

In some embodiments, the formula for determining a user's priority classmay be as simple as ranking the various available classes. In that case,a user's priority category is simply the highest ranked class to whichthe user belongs. Alternatively, the current user may manually select auser's priority class, or a more complex formula may be used to takevarious factors about users into consideration. In the case of afeatured user with an active alternative profile, that featured user'spriority class may be determined based on the assumption that thefeatured user is actually a common user. Accordingly, when viewed by acurrent user, the featured user may appear as a common user wouldappear.

Accordingly, the networking system 300 may classify users, enable usersto easily identify the classes of other users, and facilitate convenientinteractions between users of various classes.

Chat Bidding System

The chat bidding system 330 of the web site 305 may provide an organizedcommunity in which common users may interact with a featured user. FIG.6 illustrates a block diagram of an exemplary chat bidding system 330 ofthe web site 305. As shown in FIG. 6, an instance of the chat biddingsystem 330, a chat bidding session, may comprise a plurality of commonuser accounts 610, a tasks queue 620, and a featured user account 630.

Each chat bidding session of the chat bidding system 330 may comprise aplurality of common users 615 and at least one, and preferably only one,featured user 635. Through common user accounts 610, the common users615 may pose tasks to the featured user 635. The tasks queue 620 maystore the posed tasks or references to the posed tasks. Through thefeatured user account 630, the featured user 635 may be presented withthe tasks, preferably one at a time, and may choose whether to respondto each task as it is presented.

FIG. 7 illustrates a flow diagram of an operation 700 of the chatbidding system 330 according to an exemplary embodiment of thenetworking system 300. As shown in FIG. 7, at 710, the web site 305 mayreceive a task posed by a first common user 615. The task may beaccompanied by a pledge from the common user 615, and a bid valuecorresponding to the pledge may be associated with the task. At 720, thetask may be inserted into an appropriate position of the queue 620 basedon the task's associated bid value. A second task may be received from asecond common user 615 at 730, and at 740, the second task may also beinserted into an appropriate position of the queue 620. At 750, the website 305 may present the featured user 635 with a priority task, whichis the task currently at the top of the ordered queue 620. The featureduser 635 may choose to respond to the priority task, or to skip thepriority task. In an exemplary embodiment of the chat bidding system330, common users 615 whose tasks are skipped may receive refunds fortheir pledged credits. At 760, the web site 305 may respond according tothe featured user's decisions to skip or respond to the priority task.This may comprise accepting the featured user's response to the task orindicating that the priority task has been skipped.

Referring now back to FIG. 6, the common users 615 may pose tasks to thefeatured user 635. Each task may comprise a question, comment, orrequest of the posing common user 615. In posing a task, a common user615 thereby requests that the featured user 635 respond to the posedtask. Tasks may be posed in various formats. For example, a task may bea typed question, an audio challenge or other request, or various otherformats for prompting a response from the featured user 635. The website 305 may receive the tasks and, as described further below, maystore the tasks in an ordered manner through use of the queue 620.

A common user 615 may associate a bid with a posed task. The bid ispreferably a pledge of credits from the common user's credit account. Ifthe common user 615 is also a sponsored user, the bid may be a pledge ofcredits from an associated sponsoring user's credit account instead. Inpledging a credit amount, the common user 615 may commit to purchase thefeatured user's response to the task for the pledged amount or,alternatively, may commit to purchase an opportunity to present the taskto the featured user 635 for the pledged amount. If the common user 615does not associate the task with a bid, a bid value for the posed taskmay be set to zero. A first exemplary embodiment of the chat biddingsystem 330 debits the common user's credit account regardless of whetherthe featured user 635 responds to the common user's task. An alternativeexemplary embodiment of the chat bidding system 330, however, debits thecredit account only if the featured user 635 is eventually presentedwith the common user's task or, alternatively, only if the featured user635 responds to the common user's task.

The tasks queue 620 may store the tasks or references to the tasks.Storage space for the tasks queue 620 may be provided on the serverassembly 150. In the tasks queue 620, tasks may be ordered based atleast partially on their bid values. In other words, a first task with afirst bid value may be ranked higher than a second task with a lower bidvalue. When a new task is posed by a common user 615, such new task maybe inserted into the tasks queue 620 based on a ranking of the bid valueof the new task. In an exemplary embodiment of the chat bidding system330, if the new task has a bid value equal to a bid value of apreviously-posed task already in the tasks queue 620, the new task maybe ranked behind the previously-posed task. The web site 305 may notifythe common user 615 of positions of his tasks in the queue 620.Additionally, the web site 305 may allow the common user 615 to alterthe bid values of his tasks and, thereby, potentially modify thepositions of his tasks in the tasks queue 620. The web site 305 may alsodisplay to the common user 615 an amount of credits required to increasea task of the common user 615 to a certain rank in the tasks queue 620.In some exemplary embodiments, bids for previously submitted tasks maybe increased but not decreased.

A predetermined number of highest ranked tasks in the queue 620 may havea fixed ranking order at the top of the queue 620. For example, and notlimitation, the top N tasks may be fixed such that a bid modification ofa previously lower-ranked task may not affect the positions of such topN tasks. Further, the top N tasks may be presented to the featured user635, according to their rank amongst the other top N tasks.

In some implementations of the chat bidding system 330, fixing ranks ofthe top N tasks may entail removing the top N tasks from the tasks queue620, and inserting them into a standby queue. Tasks in the standby queuemay be ordered according to when they were removed from the tasks queue620, and may be presented to the featured user 635 in an order in whichthey were inserted into the standby queue. In other words, the standbyqueue may be a first-in-first-out queue, and after a task is removedfrom the standby queue for presentation to the featured user 635, ahighest ranked task in the tasks queue 620 may be removed from the tasksqueue 620 and inserted into the standby queue. In other implementations,fixing ranks of the top N tasks may entail setting fixed positions forsuch top N tasks within the queue 620 and restricting resorting of suchtasks. In either of these implementations, any resorting or rearrangingof the queue 620 may not affect the positions of the top N tasks.

Those skilled in the art will recognize that a queue may be implementedin various manners and through use of various data structures. Thoseskilled in the art will further recognize that a queue may refer tocertain types of related data, which may, but need not, be stored incontiguous physical space. Accordingly, as used herein, the standbyqueue of the chat bidding system 330 may refer to a set of data storeddistinct from the tasks queue 620, or to a set of data sharing physicalspace with the tasks queue 620.

Fixing ranks of the top N tasks may incentivize common users 615 topledge high bid values for their tasks, because after such tasks reach apredetermined rank, their positions become fixed. Preferably, N is asmall number, such as two. A large value of N may discourage commonusers 615 by making too many of the top positions unreachable.

To increase efficiency of the networking system 300, data regardingposed tasks may be stored on the client computer 102, in addition to theserver assembly 150. A client-side application may run at the clientcomputer 102, and may cache task data on the client computer 102. In anexemplary embodiment of the networking system 300, client-side cachingmay occur locally on the client computer 102 by storing task data in anarray in the order in which the tasks were posed. The array may containtask data including, for example, question text, bid amount, and currentposition in the tasks queue 620. The order in which tasks are stored inthe array may be retained when a web page of the chat bidding session isreloaded. The client-side cache may be updated at various occurrences,such as a rank change or an update to task text or bid amount.

The web site 305 may present the featured user 635 with the prioritytask. The priority task may be the highest ranked task in the tasksqueue 620. Alternatively, if the top N tasks are removed from the tasksqueue 620 and inserted into the standby queue, the priority task may bethe highest ranked task in the standby queue. The featured user 635 maybe able to view a predetermined number of other posed tasks in additionto the priority task, but preferably, the featured user 635 must act onthe priority task before being presented with any other tasks. Alsopreferably, the featured user 635 may view only the top N tasks, whichhave fixed position in the order in which they will be presented to thefeatured user 635. In such embodiments, the featured user 635 may bepermitted to select presented tasks out of order. For each viewabletask, the featured user 635 may also view statistics related to thetask, such as the associated bid value and how long the task has been inthe queue 620.

After being presented with the priority task, the featured user 635 maychoose to respond to the priority task or to skip the priority task. Ifthe priority task is skipped, the featured user 635 may not have anotheropportunity to respond to such task unless it is again posed by a commonuser 615. By presenting the featured user 635 with each task only once,the web site 305 may provide an organized manner for the featured user635 to handle a small or large number of tasks. Additionally, commonusers 615 may be encouraged that their tasks may eventually be presentedto the featured user 635 and may, therefore, more confidently pledgecredits towards their tasks to increase a possibility that their taskswill be viewed. In an alternative embodiment of the chat bidding system330, however, the featured user 635 may be entitled to temporarily skipa task and have it represented later, preferably after the followingtask.

When a task becomes the priority task, the common user 615 who posedsuch task may become a recognized common user 615. In that case, datarelating to the recognized common user 615 may be displayed to othercommon users 615 and to the featured user 635. Such data may include,without limitation, the recognized common user's username and picture.Additionally, other users, both common 615 and featured 635, may have anopportunity to follow a web hyperlink and, thereby, view the recognizedcommon user's full profile on the web site 305. Accordingly, therecognized common user 615 may be rewarded for his pledge in that allother parties may know who posed the priority task. If the common user615 who posed the priority task is a sponsored user, the associatedsponsoring users may be recognized along with the common user 615 whoposed the task.

As mentioned above, the featured user 635 may choose to respond to thepriority task. The type of response given by the featured user 635 maydepend on the type of task posed. For example and not limitation, if thetask is a question, the featured user 635 may answer the question, andif the task is a request, the featured user 635 may comply with therequest. The web site 305 may receive the response of the featured user635 in various ways. For example, the web site 305 may receive anddisplay an answer to a question in the form of text. Alternatively, theweb site 305 may receive the featured user's compliance with a taskedrequest through, for example, a webcam or other recording media, inwhich case the result may be displayed in a video or audio format.

A role of the featured user 635 may be similar to a role of a chatmoderator. For example, the featured user 635 may initiate the chatbidding session and may prompt tasks from the common users 615. Wheninitiating a chat bidding session, the featured user 635 may select acharity to share in revenues generated by the chat bidding session. Thefeatured user 635 may be able to change the benefiting charity duringthe chat bidding session. Credits deducted from credit accounts of thecommon users 615 for posed tasks represent revenues of the chat biddingsession. In predetermined percentages, such revenues may be dividedamong the web site manager 308, the featured user 635, and, ifindicated, the selected charity.

The featured user 635 may also have access to a synchronous alert toolon the web site 305. For example, when initiating a chat biddingsession, the featured user 635 may issue a mass notification to allcommon users 615 or to a predetermined set of common users 615, tonotify such common users 615 of the chat bidding session. In anexemplary embodiment of the chat bidding system 330, the synchronousalert tool issues a pop-up alert to common users 615.

A common user 615 may view various elements of the chat bidding session.For example, the web site 305 may display to the common user 615 a nameand biography of the featured user 635. The web site 305 may alsodisplay responses for each task to the plurality of common users 615, asin a group chat session. In other words, if the featured user 635responds to a task of a first common user 615, such response may bedisplayed to all common users 615 in a virtual group environment of theweb site 305. Additionally, each common user 615 may view and scrollthrough his own posed tasks. The common user 615 may view the queueposition of each of his tasks and may modify the bid amount of each ofhis tasks. Optionally, the common user 615 may also have access to acomplete list of posed tasks from the plurality of common users 615. Insome exemplary embodiments of the chat bidding system 330, a firstcommon user 615 may be able to pledge his credits to a task posed by asecond common user 615. In this case, the second common user 615 neednot be a sponsored user. Accordingly, the first common user 615 mayincrease the bid value and, potentially, the rank of a task of thesecond common user 615. Additionally, in such a scenario, the web site305 may acknowledge both the second common user 615 and the first commonuser 615 when the task is featured and presented to the featured user635.

Throughout the chat bidding session, the web site 305 may displayvarious statistics related to the chat bidding session. For example, andnot limitation, the web site 305 may display the total credits raisedduring the chat bidding session up to the current point in time, thetime elapsed in the bidding session, the number of posed tasks not yetpresented to the featured user 635, the name of the selected charity,the average time the featured user 635 has taken to act on or respond toeach presented task, and the estimated time remaining in the chatbidding session. At any point in time, the featured user 635 may pausethe chat bidding session and, thereby, pause any running clocks utilizedfor calculating statistics related to the chat bidding session.

FIG. 8 illustrates a flow diagram of a process 800 of a featured user635 initiating and participating in a chat bidding session, according toan exemplary embodiment of the chat bidding system 330 of the web site305.

As shown in FIG. 8, at 801, the featured user 635, such as a celebrity,may initiate the chat bidding session. This may occur when the featureduser 635 selects an appropriately labeled button, such as a buttonlabeled “Create StarChat.” At 802, a pop-up or dialog may appearallowing the featured user 635 to create the new chat bidding session.At 804, the featured user 635 may select a charity to benefit from thechat bidding session, and may determine a duration for the chat biddingsession. At 806 and 808, the networking system 300 may create the chatbidding session using the validated charity and duration selections.

Cache object validation may occur at 810. If a cache object does notexist, the networking system 300 may create a new cache object formanaging the chat bidding session. To improve performance, thenetworking system 300 may cache objects on the server assembly 150 sothat they can be used and manipulated quickly. Upon creation of a newchat bidding session, the networking system 300 may determine whether adialog for a chat bidding session has already been created. If not, at812, a chat bidding session dialog, in which tasks and responses may bedisplayed, is created and added to the cache. Then, the next time thedialog is requested, it may be retrieved from the cache. Upon creationof the new dialog, at 814, the networking system 300 may notify allonline users of creation of the chat bidding session.

A new chat icon may be created at 816, and may be viewable by the commonusers 615. At 818, the networking system 300 may direct the featureduser's web client 124 to a web page of the chat bidding session. At 820,the featured user's information, such as name and occupation, may beloaded into the chat bidding session for viewing by the common users615. At 822, the featured user 635 may await questions and tasks fromthe common users 615. While there are no new questions or tasks, asshown at 824, certain data about the chat may automatically update. Suchdata may include, without limitation, elapsed time, average time torespond to a question or task, and estimated time remaining. Preferably,this data is maintained and displayed as needed and appropriatethroughout the chat bidding session.

At 826, a process of acting on questions and other tasks of common users615 may begin. The networking system 300 may determine whether aquestion or task has already been chosen by the featured user 635 at828. At 830, if a question or task is already chosen, the question ortask is added to the tasks queue 620 in cache to be stored for efficientfuture use. At 832, the tasks queue 620 may be re-sorted based on bidvalues relating to one or more newly inserted tasks.

Returning to 828, alternatively, if a question or task has not yet beenchosen, a question or task may be retrieved, at 834, along with relateddata, such as data pertaining to the common user 615 who posed thequestion or task. At 836, the question or task data may be displayed sothat the featured user 635 may respond. At 838, a notification may besent to the common user 615 who posed the question or task, informingthe common user 615 that his question or task is the priority task. At840, this priority task may be removed from the tasks queue 620, and at842, the tasks queue 620 may be updated to reflect that the prioritytask has been removed.

FIGS. 9A-9B illustrate flow charts depicting further exemplary functions900 of the featured user 635 during the chat bidding session. At 901, ifthe featured user 635 previously elected a charity benefactor, thefeatured user 635 may change the selected charity from within the chatbidding session. Changing the charity may be initiated when the featureduser 635 selects a “Change Charity” button at 902. Then, a pop-up ordialog may appear, enabling the featured user 635 to select a newcharity. The pop-up or dialog may provide a list of approved charitiesfrom which the featured user 635 may choose. At 904, the featured user635 may select a new charity, and the newly selected charity may beverified at 907. This validation step may include, for example,verifying that the charity is a valid charity associated with thefeatured user 635. At 908, a notification of the new charity may betransmitted to all common users 615 related to the chat bidding session,and 910, all common users 615 and featured users 635 may be updated withthe newly selected charity.

In an exemplary embodiment of the present invention, changing thebenefiting charity of a chat bidding session may not affect adistribution of the revenues generated through the chat bidding sessionbefore the change occurred. In other words, a first charity may benefitfrom the chat bidding session for the time period during which suchfirst charity was specified as the benefiting charity. If the benefitingcharity is changed to a second charity during a chat bidding session,only revenues after the change may be generated for the benefit of thesecond charity.

At 912, the featured user 635 may have an ability to use the synchronousalert feature. This feature, as discussed above, may enable the featureduser 635 to send a message to all common users 615 participating in thechat bidding session. After selecting the synchronous alert feature,e.g. a “StarBlaster” button, at 912, a pop-up window may be presented tothe featured user 635 at 914. At 916, the featured user 635 may provideand submit a message for the common users 615. At 918, the message maybe transmitted to all common users 615 involved in the chat biddingsession.

As mentioned above, the featured user 635 may have an ability to selectthe duration of the chat bidding session. At 920, the featured user 635may change such duration. He or she may accomplish this by selecting a“Change Duration” button. At 922, a pop-up may appear, allowing thefeatured user 635 to modify the duration. At 924, the featured user 635may enter the modified duration information, which may then be validatedat 926. Upon approval of the new duration, a notification may be sent toall users in the chat bidding session at 928 and at 930. If the chatbidding session displays an end time to the common users 615, such endtime may be updated in accordance with the new duration.

As at 932 and 934, the featured user 635 may skip the priority task,which may be a question or other item prompting a response. For example,after the featured user 635 selects a “Skip Question” button at 932, thequestion or task may be removed from the cache at 934. Then, a newpriority task may be presented to the featured user 635.

At 936, the featured user 635 may opt to end pledging in the chatsession. For example, the featured user 635 may select a “SuspendPledges” button. This option may prevent common users 615 from posingadditional tasks, and may additionally prevent pledge increases forqueued tasks. At 938, the cache may be updated in response to thefeatured user's indication that pledges are no longer allowed, andaccordingly, the networking system 300 may no longer accept newquestions or other tasks from the common users 615. Next, at 940 and942, a notification may inform the common users 615 that no new tasksmay be posed in the chat bidding session. In an exemplary embodiment ofthe chat bidding system 330, the featured user 635 may be required tocontinue acting on posed tasks until all tasks with non-zero bid valuesare acted upon. Common users 615 whose tasks remain in the tasks queue620 after the featured user 635 exits the chat bidding session mayreceive refunds for their pledged credits.

Turning to 944, an exemplary process of responding to a posed questionor task is depicted. After the question or task is answered at 946, aresponse is displayed via the chat bidding session. At 948, the questionor task may be removed from the cache, and at 950, the task and responsemay be stored in the cache as answered. At 952, the task and response,or question and answer, may also be stored in the database. Then, at954, notification of such response may be sent to the common users 615participating in the chat bidding session. At 956, common users 615 andfeatured users 635 may be informed that a response to the priority taskhas been issued, and the task and corresponding response may beavailable for viewing.

The featured user 635 may terminate the chat bidding session, such as byselecting an “End Chat” button at 960. After which, a notification maybe issued to the common users 615 in the chat bidding session at 962.The common users 615 may then receive notification that the chat hasended at 964. At 966, a record of the chat bidding session dialog may beremoved from the cache. At 968, all pledges associated with unansweredtasks may be voided when the chat bidding session ends at 970.

FIG. 10 illustrates an exemplary process 1000 of a common user 615joining and viewing an exemplary chat bidding session. As shown in FIG.10, at 1001, the common user 615 may elect to join a particular chatbidding session. At 1002, the server assembly 150 may redirect thecommon user 615 to an appropriate web page for the chat bidding session,and the common user 615 may be added to a user list of the chat biddingsession at 1004. The common user 615 may then be presented with tasks towhich the featured user 635 has previously responded in the chat dialogat 1006. Additionally, questions and tasks to which the featured user635 previously responded may appear in an “asked questions” area of theweb page at 1008.

At 1010, the networking system 300 may enter a cycle of updating ranksof posed tasks. Such updating may ensure that the tasks, as displayed onthe web site 305, reflect accurate rankings based on updated bid valuesfrom common users 615. Updating may be implemented, preferably behindthe scenes and out of view of the users 615 and 635, by providing aquestion selector on the client computer 102 to iterate through tasks inthe local tasks queue 620. Each web client 124 may provide metadata tothe server assembly 150 describing changes to bid values and task ranks.In each iteration, at 1010, a web client 124 may determine whether thequestion selector references a posed task. If so, at 1012, an updatedrank of the task may be retrieved from the tasks queue 620 on the serverassembly 150. The rank of the task referenced by the question selectormay then be updated on the web client 124 to reflect current bid valuesat 1014.

FIG. 11 illustrates an exemplary process 1100 of a common user 615participating in an exemplary chat bidding session. At 1114, the commonuser 615 may use arrows, or similar selectors, to cycle through taskspreviously posed by that particular common user 615. At 1116, thenetworking system 300 may determine whether questions or other tasksposed by other common users 615 exist in the queue 620. If no such tasksexist, the networking system 300 may clear areas of the cache used fordisplaying tasks and their pledges and ranks. The common user 615 maythen pose new tasks to the featured user 635. Alternatively, if one ormore tasks remain in the tasks queue 620, as at 1120, data regardingsuch tasks may be retrieved from the cache and then displayed at 1122.Then, when the common user 615 enters a question or other task at 1124,the networking system 300 may insert such question or other task intothe tasks queue 620. If the newly posed task has not been previouslyposed in the chat bidding session, the web page of the chat biddingsession may then be updated with data regarding the newly posed task ofthe common user 615. Otherwise, if the task was previously posed, thetask and related data, such as an associated bid value, may be retrievedfrom the cache at 1132, and then displayed on the web page of the chatbidding session at 1134.

Preferably, the client computer 102, such as that used by the commonusers 615 or the featured user 635, and the server assembly 150 interactin the chat bidding session through a service executing a dynamicupdate. This service may enable the web page of the chat bidding sessionto update without user interactions, such as clicking a “Refresh” buttonon the web client 124. The dynamic update service may enable the commonuser 615 to view real-time positions of his tasks in the queue 620, aswell as real-time data for various other statistics viewable to thecommon user 615. The dynamic update service may enable the featured user635 to view real-time data related to, without limitation, any or all ofthe following: number of tasks in the tasks queue 620, number of queuedtasks associated with bids, elapsed time of the chat bidding session,estimated time to respond to all queued tasks, average time to respondto each task, amount of money raised, number of common users 615 viewingthe chat bidding session, and various other statistical data related tothe chat bidding session

Performance Bidding System

Through the performance bidding system 340, users may request to performon the web site 305, and may pledge credits to determine an order inwhich they may be allowed to perform. Such pledged credits may bedirected towards a benefiting charity or may be paid to the web site 305for the opportunity to perform. Alternatively, credits may be dividedbetween the web site 305 and the benefiting charity. In some exemplaryembodiments, the benefiting charity, if any, may be predetermined, andthe users may be notified of information regarding the charity.

The performance bidding system 340 may be available to both common users615 and featured users 635. Through the performance bidding system 340,common users 615 may have an opportunity to perform for featured users635 and other common users 615. Similarly, featured users 635 may havean opportunity to perform for common users 615 and other featured users635. Users participating in the performance bidding system 340, but notcurrently queued for a performance on the web site 305, are hereinreferred to as observers. The users queued for performances are hereinreferred to as performers. Together, performers and observers may makeup the participants of the performance bidding system 340.

The performance bidding system 340 of the web site 305 may function insome manners similar to the chat bidding session. Similarly to the chatbidding system 330, the performance bidding system 340 may comprise aqueue, specifically a performance queue, and a plurality ofparticipating users.

When a performance request reaches the top of a performance queue, theuser making the performance request may perform live for otherparticipants. During a performance, the networking system 300 mayprovide the performing user with music and lyrics, as in a karaoke-styleperformance. If a non-karaoke type of performance is desired, the website 305 may provide other, appropriate support for the performance. Forexample, if the performing user indicates that she would like to performin spoken word, the web site 305 may provide soft background music asindicated by the performing user. The performing user may provide one ormore recording devices, such as a webcam and a microphone, and theserver assembly 150 may receive media representing the performance.Preferably, such media is streaming media. The web site 305 may presentthe performance, preferably streaming, to the observers.

Users who make performance requests may be provided with a menu ofselections for supporting their performance. For example, a userrequesting to perform may be presented with a list of songs for the website 305 to provide music and lyrics. Upon selecting specificperformance support for a performance, the user's username and supportselections, such as a song title, may appear in a status section of aweb page of the performance bidding system 340 to identify the user'sposition in the performance queue. All other queued performers, oralternatively, a predetermined number of highest ranked performers inthe performance queue, may also appear in the status section, therebyproviding participants with data regarding expected performances.

Through the performance bidding system 340, the web site 305 may displaydata regarding the performers, observers, or all participants. Forexample, and not limitation, the web site 305 may display the totalnumbers of performers and observers. The web site 305 may also displaystatistics of performers or of the total participating users, such asdisplaying geographic statistics of the performers or of allparticipants. This may give participants an estimate of the geographicrange of the performers, and may give performers a geographic range ofthe observers.

Upon making a performance request, a user may pledge credits to therequest and, thereby, associate the request with a bid value. If theuser requesting to perform is a sponsored user, then the pledged creditsmay be credits from an associated sponsoring user's account. If no bidvalue is provided with a performance request, the request may be placedat the bottom of the performance queue. However, a performer mayincrease her position in the queue by increasing her pledge value aboveother another performer's pledge value. Performers may rise in theperformance queue as others perform and are, consequently removed fromthe queue. A performer's position in the queue may be dynamic, as allperformers may increase their bid values to escalate their own positionsin the performance queue. Therefore, a performer's queue position mayperiodically change and be updated accordingly in the status section.

A bidding dialog box on the web site 305 may provide performers withmeans to increase their pledges and, thereby, potentially increase theirpositions in the performance queue. The bidding dialog box may displayto each performer an amount of credits required to increase theperformer's queue position to a certain rank in the performance queue.After a performer attains one of the top X positions in the performancequeue, the performer's position may become locked. Locking the top Xpositions in the performance queue may be implemented in variousmanners, including those described above with reference to the top Npositions of the tasks queue 620. Performers with the top X lockedpositions may be able to perform in succession regardless of pledgeincreases of participants. At a point in time, the top X performers,along with their support selections, may be displayed in the statussection of the web page of the performance bidding system 340.

While a user is performing on the web site 305, data from her profilemay be displayed to participants of the performance bidding system 340.Participants may also have an opportunity to follow a web hyperlink and,thereby, view the performing user's full profile on the web site 305.Participants may then be able to learn more about the performing userand may leave feedback on the performing user's profile.

At the end of each performance, a rating window may automatically bepresented to the participants. Through the rating window, theparticipants may rate the performance or leave feedback regarding theperformance. Top-rated performances may be stored on the server assembly150 and accessible for replay by each participant.

FIG. 12 illustrates a flow diagram of a process 1200 of the performancebidding system 340, according to an exemplary embodiment of thenetworking system 300. As shown in FIG. 12, at 1202, a participant mayenter a lobby, or introductory web page, of the performance biddingsystem 340 of the web site 305. The participant may participatepassively by requesting, receiving, and viewing streaming media of thecurrent performing user at 1204. The participant may elect to become aperformer at 1206. At 1208, the participant may be presented with aselection of support material, such as a list of songs from which theparticipant may select a song to perform. After the participant selectssupport material, the user's username and support material may beinserted into the last position of the performance queue, at 1210, if nocredits are yet pledged. The performance queue may be maintained anddynamically updated at 1212. At 1214, the participant may be offered anoption to pledge credits, or additional credits, to escalate herposition in the performance queue. If the participant bids credits toescalate her position, at 1216, the networking system 300 may determinewhether the bid is sufficient to raise the participant's position in theperformance queue. If the bid is sufficient, the process 1200 returns to1212 and updates the performance queue.

When a performance ends at 1220, a next performer in the performancequeue may be alerted. Additionally, the queue may be updated, and arating dialog box may be displayed at 1222, providing participants anopportunity to rate the previous performer and to provide comments aboutthe performance. Accordingly, participants, including the previousperformer, may be provided with instant feedback from otherparticipants. Viewing participants may complete a rating form in thedialog box or may bypass completing the rating form at 1228.

When a participant performs, streaming media, such as audio and video,of the performer may be presented to all viewing participants at 1224.In some instances, the participant may be provided with background musicand lyrics at 1226.

Accordingly, users of the networking system 300 may interact with oneanother by performing for one another, viewing such performances, andcommunicating regarding such performances.

Telephony Switching System

In accordance with an exemplary embodiment of the telephony switchingsystem 350, parties may contact one another anonymously. The telephonyswitching system 350 may enable a party to limit calls from certainusers and groups of users, and according to predefined schedules. Thisfeature of the web site 305 may be especially beneficial for featuredusers 635. Through the telephony switching system 350, a featured user635 may place or accept a call to or from a common user 615 whilemaintaining a concealed phone number. Additionally, through predefinedscheduling rules, the featured user 635 may block all calls duringcertain time periods. Furthermore, common users 615 may transition achat session to a telephone call without compromising the privacy commonto chat sessions.

In an exemplary embodiment of the networking system 300, a calling partymay request a connection, such as a telephone chat, to a receivingparty. Prior to attempting to forge the connection, the networkingsystem 300 may verify that the receiving party is willing to accept theconnection from the calling party. Once verified, the networking system300 may place a call to each of the calling party and the receivingparty, and may then patch the two calls together so that each of the twoparties can engage in a chat without divulging contact information, suchas a telephone number, to the other party. Alternatively, the callingparty may initialize the connection by contacting a service center andrequesting to be connected to the receiving party via a communicationdevice. In such an embodiment, the service center may initiate a call tothe receiving party and patch that call to the calling party.

Before a user may utilize the telephony switching system 350, acommunication device of the user may need to be registered with thetelephony switching system 350. FIG. 13A illustrates a process 1300 ofregistering a communication device with the telephony switching system350. As shown in FIG. 13A, at 1301, the user of the telephony switchingsystem 350 may request that the communication device be registered. At1302, the telephony switching system 350 may register the communicationdevice on a database of the server assembly 150. At 1304, the telephonyswitching system 350 may create a unique identifier associated with thecommunication device. At 1306, a message may be displayed on the website 305 notifying the user of the unique identifier and itsavailability for use. At 1308, the user may either assign his ownpersonal identification number (“PIN”) or request that the telephonyswitching system 350 create a PIN for the user. At 1310, telephonyswitching system 350 may determine whether to create a PIN or,alternately, whether the user has submitted a PIN for validation. If thetelephony switching system 350 was asked to assign a PIN, such a PIN iscreated and assigned by the telephony switching system 350 at 1312.Otherwise, the user assigned PIN may be validated. At 1320, the web site305 may display that the PIN is active and ready for use.

Accordingly, after completing the registration process, thecommunication device may be associated with a unique identifier and aPIN. Generally, the unique identifier may be used to identify a callingparty when a connection is requested via the telephony switching system350. The PIN, on the other hand, may be used to identify a receivingparty. In other words, when attempting a connection, the calling partymay provide a unique identifier to identify himself, and may provide aPIN to identify the receiving party. Accordingly, the calling party maybe required to receive a PIN from the receiving party before connectingto the receiving party. Each receiving party may request and receivemultiple PINs from the telephony switching system 350. According towishes of the receiving party, each PIN may serve a distinct purpose.For example, a first PIN may be distributed to family members forcontacting the receiving party, and a second PIN may be distributed tobusiness associates for contacting the receiving party. This will bedescribed in further detail below.

FIGS. 13B-13C illustrate block diagrams of exemplary embodiments of thetelephony switching system 350. As shown in FIG. 13B, an exemplaryembodiment of the telephony switching system 350 may generally compriseat least two communication devices 1330, a service center 1360, and atelephony switch 1370.

As shown in FIG. 13B, the calling party 1380 may use the firstcommunication device 1340 to communicate with the service center 1360.The service center 1360 may be in communication with the telephonyswitch 1370. The telephony switch 1370 may be in communication with thefirst communication device 1340 and the second communication device1350, and may connect the first communication device 1340 to the secondcommunication device 1350. For purposes of FIGS. 13B-13C, thecommunication devices 1330 are already registered with the telephonyswitching system 350.

The communication devices 1330 may include a first communication device1340 and a second communication device 1350. For purposes of anexemplary embodiment of the telephony switching system 350,communication devices 1330 may comprise various devices capable ofcommunicating over a communications network, such as a telephone networkor the internet. Each communication device 1330 may be a wiredtelephone, wireless telephone, cellular telephone, satellite telephone,voice over IP (“VoIP”) phone, PDA, soft phone, computer, or other devicecapable of audio and/or video communications. The first communicationdevice 1340 may be associated with a first phone number and a callingparty 1380. The first phone number identifies the first communicationdevice 1340. Similarly, the second communication device 1350 isassociated with a second phone number and a receiving party 1390. Thesecond phone number identifies the second communication device 1350.

The service center 1360 may comprise one or more hardware or softwaredevices, or various combinations thereof, capable of receiving andstoring registrations relating to communication devices 1330, managingsuch registrations, analyzing connection requests relating to registeredcommunication devices 1330, and initiating and managing connections.

The telephony switch 1370 may comprise various telephone exchanges,switches, or combinations thereof. For example, and not limitation, thetelephony switch 1370 may be a private branch exchange (“PBX”). Thetelephony switch 1370 may connect the calling party 1380 to thereceiving party 1390 if such a connection is deemed allowed.

In an exemplary embodiment of the telephony switching system 350, thetelephony switch 1370 may comprise one or more PBX switches trunked toother telephony switches and telephony service centers with various PBXslocated around the world. Trunks may allow multiple calls to be combinedinto a single channel and be delivered to other PBXs either in the sametelephony switch 1370 or other telephony switches having availablechannels to VoIP termination providers or public switched telephonenetwork (“PSTN”) terminations. In addition, the telephony switch 1370may provide trunks and termination end points to provide high qualityand low cost termination to communication devices 1330. The terminationend points and trunks may also be provided through a third party VoIPtermination or PSTN. In an exemplary embodiment, the PBX implementationmay be a software system allowing existing telephony infrastructure tointeract using VoIP standards.

In some exemplary embodiments of the telephony switching system 350, theservice center 1360 and the telephony switch 1370 may be integratedtogether. For example, the service center 1360 may comprise a PBX forproviding the call-handling for users requesting communications withother users. Calls may traverse digital circuits, analog interfaces,VoIP networks, or various other networks for delivering communications.Digital circuits may be defined telephony standards, such as T1 linescarrying 24 channels of voice to standard telephony companies. Analoginterfaces may provide single channels of voice for delivery to thepublic switched telephone network (PSTN). VoIP protocols, such as SIP,IAX, H.323, and others, may enable audio, metadata, and video to bedigitized, secured, and compressed for delivery over computer networksto other service centers or other termination endpoints. These deliverymediums may enable the PBX in the service center 1360 to connect two ormore parties anonymously.

FIG. 14 is a flow diagram illustrating a method 1400 of handling aconnection request from the calling party 1380 to connect to thereceiving party 1390, according to an exemplary embodiment of thetelephony switching system 350. At 1410, the service center 1360receives a connection request from the calling party 1380 to connect tothe receiving party 1390. Such communication request may be made by thecalling party 1380 through the first communication device 1340.Alternatively, the communication request may be made by the callingparty 1380 via a web interface. At 1420, the service center 1360 maydetermine whether a connection is allowed given predetermined variables.Such variables may include certain contact rules preset by the receivingparty 1390. For example, and not limitation, each user may provide alist of users permitted to call, a list of users not permitted to call,times when calls are allowed, or other suitable calling criteria. If theconnection request is not allowed, the service center 1360 may notifythe calling party 1380 of the denial, as at 1430. Otherwise, if theconnection request is approved, at 1440, the service center 1360 mayforward the connection request to the telephony switch 1370. At 1450,the telephony switch 1370 may connect to the second communication device1350 and, therefore, to the receiving party 1390 using the secondcommunication device 1350. Finally, at 1460, the telephony switch 1370may patch together its connections to the calling party 1380 and thereceiving party 1390, such that the two parties 1380 and 1390 are incommunication with each other. If the receiving party 1390 does notanswer, the calling party 1360 may be permitted to leave a voice messagewithin the receiving party's video/voice mailbox.

Referring now back to FIG. 13B, communication devices 1330, such as thefirst and second communication devices 1340 and 1350, may be registeredwith the service center 1360. Registrations may be communicated to theservice center 1360 through various manners. For example, and notlimitation, registration of the first communication device 1340 may becommunicated to the service center 1360 through a phone call, such as bythe calling party 1380 calling the service center 1360 and providingregistration information.

Alternatively, registration may be accepted through a web client 124.The web client 124 may receive registration information and send it tothe server assembly 150. The server assembly 150 may be part of, or incommunication with, the service center 1360. Alternatively, the servicecenter 1360 may be part of the server assembly 150. The server assembly150 may provide the registration information to the service center 1360.Registration information for a communication device 1330 may include,without limitation, a phone number associated with the communicationdevice 1330, an account identifier, and a set of contact rules.

The account identifier may comprise information for identifying a useraccount on the web site 305. The specified user account may then beassociated with the communication device 1330. As discussed above, anaccount user, such as the calling party 1380, may have a credit accountassociated with the user account. The credit account may track a numberof credits available to the associated user for purchasing services fromthe web site 305. By associating the user account with the communicationdevice 1330, credits available to the user of the user account may alsobecome available for the purpose of purchasing connections through thetelephony switching system 350. Additionally, credits may be charged forthe duration of connections initiated through the telephony switchingsystem 350.

In the case of a sponsored user, credits used by the sponsored user forconnections through the telephony switching system 350 may be charged toan account of an associated sponsoring user. In some embodiments, thesponsoring user may specify, such as in his or her sponsor guidelines,that credits used by the sponsored user for these connections must belimited to interactions with the sponsoring user. If such aspecification is made, then the telephony switching system 350 may denyconnections requested by the sponsored user to users other than thesponsoring user, if such connections would otherwise be charged to thesponsoring user.

As a part of a registration, the set of contact rules may indicate whomay connect to the communication device 1330, and when such connectionsmay occur. Various rule types may be included in the contact rules. Forexample, and not limitation, the contact rules for the receiving party1390 or the second communication device 1350 may specify thatconnections may be made from the first communication device 1340 onlyduring certain hours. For purposes of establishing contact rules, thereceiving party 1390 may refer to the first communication device 1340by, for example, its associated phone number, its unique identifier, ora username or other alias of the receiving party 1390. For additionalexample, the contact rules may specify that users of a predefined groupmay not connect to the second communication device 1350, or that usersof the predefined group may connect to the second communication device1350 only during specified hours. The contact rules may specify that thefirst communication device 1340, or users of the predefined group, maynever connect to the second communication device 1350 or, alternatively,may connect to the second communication device 1350 at any time. Thecontact rules may also specify categories of allowed or disallowedcalls, such as conference calls, faxes, or calls from cellulartelephones. One skilled in the art will recognize that the contact rulesmay specify alternate handling of connection requests based on variousfactors, including, without limitation, subject matter of the call,gender of the calling party, geographic location of the calling party,and/or time of the call.

At least partially because of the wide range of potential contact rules,embodiments of the telephony switching system 350 may have wideapplication. For example, the telephony switching system 350 may be usedfor recruiting and screening employment opportunities. A potential hireemay structure contact rules around acceptable employment opportunities.For further example, the potential hiree may allow calls only fromrecruiters or employers having job opportunities in a predefinedgeographic area, with salaries over a predetermined threshold, and/orwith a predetermined set of benefits.

The contact rules may specify actions to be taken if a connection isrequested when the receiving party 1390 is unavailable and cannot,therefore, respond to a connection made through the telephony switchingsystem 350. For example, and not limitation, the contact rules mayspecify which parties are approved to leave messages, and which partiesare to be presented with a pre-recorded message from the receiving party1390. Further, the contact rules may specify alternate voicemailrecordings to be presented to alternate calling parties 1380. Aconnection may be automatically terminated if the calling party 1380 isnot approved to leave a message or to receive a pre-recorded messagewhen the receiving party 1390 is unavailable. Additionally, if a call isattempted, but the receiving party 1390 does not answer the call, thetelephony switching system 350 may terminate the call when detectingthat the receiving party's voicemail is answering the call. Suchtermination may be useful in maintaining the privacy of the receivingparty 1390 because personal information, such as the person's identityor phone number, may be present on the standard voicemail greeting. Insuch cases, the calling party 1380 may be diverted to the receivingparty's mailbox associated with the telephony switching system 350, orthe call may be terminated without allowing a message to be left.

Mailboxes may receive messages of various types. For example, and notlimitation, such mailboxes may include conventional voice mailboxes,video mailboxes, audio mailboxes, email mailboxes, and multimediamailboxes capable of receiving various types of mail. When a call to thereceiving party 1390 is unanswered, the calling party 1380 may beredirected to a voice mailbox, or may receive instructions for leaving amessage in some other media format. Through the web site 305 or over aphone call, the receiving party 1390 may have various options fororganizing, sorting, retrieving, and responding to messages, includingthose messages left through the telephony switching system 350. Forexample, the receiving party 1390 may sort messages based oncharacteristics of senders of the messages, or on other characteristicsof the messages. The receiving party 1390 may respond individually or enmasse to all messages or a set of messages. Such response may also takevarious media formats, such as video, audio, email, or multimedia.

In addition to the above, the contact rules may specify that any personwho provides a specific PIN may connect to the second communicationdevice 1350 according to a predefined schedule associated with thecaller PIN. As described above, the receiving party may have multiplePINs for distinct purposes. Multiple caller PINs may be assigned andused for various users, groups, or call types. For example, differentcaller PINs may be provided for chat sessions, for a family group, andfor a celebrity fan group. Each caller PIN may be automaticallygenerated by the service center 1360, or the receiving party 1390 maycreate the caller PIN and provide such caller PIN to the service center1360. Each caller PIN may, for example, allow unlimited uses, a specificnumber of uses, or may be given an absolute or relative terminationdate.

Connections may be requested in various ways. For example, the callingparty 1380 may call the service center 1360, which is preferablyidentified by a toll free number. When connected to the service center1360, the calling party 1380 may provide information to identify thereceiving party 1390. For example, and not limitation, the calling party1380 may enter a username for a user account of the receiving party1390, an identifying PIN associated with the receiving party 1390, theunique identifier of the receiving party 1390, or various otheridentifiers or aliases of the receiving party 1390. Preferably, theservice center 1360 receives such information from the calling party1380 via an automated service provided by the service center 1360.

If the receiving party's contact rules dictate that the calling party1380 provide a caller PIN, the calling party 1380 may be prompted toprovide such a caller PIN. In a first exemplary embodiment, the servicecenter 1360 may automatically recall the unique identifier of the firstcommunication device 1340. In an alternate exemplary embodiment, theservice center 1360 may prompt the calling party 1380 to enter theunique identifier of the first communication device 1340. The servicecenter 1360 may consider this unique identifier when determining whetherto approve the connection. After receiving the connection request, theservice center 1360 may approve or deny the connection based on datareceived from the calling party 1380 and the first communication device1340, as compared to the contact rules of the receiving party 1390.

As illustrated in FIG. 13C, and as briefly discussed above, theconnection request may also be made over the internet through use of oneor more web clients 124. Through a first web client 124, the callingparty 1380 may be logged into a user account on the web site 305.Through links in the web site 305, the calling party 1380 may request aconnection to the receiving party 1390. The calling party 1380 may notbe required to know the name or phone number of the receiving party1390, so long as the calling party 1380 can provide predeterminedidentifying information regarding the receiving party 1390. For example,and not limitation, the calling party 1380 may provide or select ausername of a user account associated with the receiving party 1390. Theserver assembly 150 may receive the connection request and may route therequest to the service center 1360 for approval. The service center 1360may approve or deny the connection based on contact rules of thereceiving party 1390.

Alternatively, the receiving party 1390 may be logged onto the web site305 when the calling party 1380 requests a connection to the receivingparty 1390. In that case, the receiving party 1390 may be notified ofthe connection request via a second web client 124 used by the receivingparty 1390. Via the second web client 124, the receiving party 1390 mayapprove or deny the connection request. The receiving party's approvalor denial may be received by the server assembly 150. If the receivingparty 1390 approves or denies the connection request via the second webclient 124, the service center 1360 need not determine whether toconnect the calling party 1380 to the receiving party 1390. If thereceiving party 1390 approves the connection, the server assembly 150may notify the telephony switch 1370 of such approval. The telephonyswitch 1370 may then connect the calling party 1380 to the receivingparty 1390, as described further below.

The service center 1360 may receive connection requests from the serverassembly 150 or from the calling party 1380. In response to suchreceipt, the service center 1360 may determine whether to honorconnection requests. After receiving the connection request of thecalling party 1380, the service center 1360 may query the contact rulesof the receiving party 1390 to determine whether the calling party 1380may connect to the receiving party 1390. If the contact rules specifythat the calling party 1380 or the first communication device 1340 mayconnect to the receiving party 1390 or the second communication device1350 at the time the connection request is made, then the service center1360 may approve the connection request. Otherwise, the service center1360 may deny the connection request. If the receiving party 1390 islogged into the web site 305 and approves the connection, the contactrules verification step may be skipped.

If a connection request is denied, the calling party 1380 may bedisconnected from the service center 1360 without being connected to thereceiving party 1390. Preferably, such a disconnection is preceded bythe service center's providing a polite message to the calling party1380 notifying the calling party 1380 that the requested connection isnot allowed. If the connection request was made via the first web client124, then the server assembly 150 may prompt the first web client 124 tonotify the calling party 1380 of the denial.

If, on the other hand, the connection request is approved, the servicecenter 1360 may communicate the approved connection request to thetelephony switch 1370. The telephony switch 1370 may then connect thecalling party 1380 to the receiving party 1390. For example, and notlimitation, the telephony switch 1370 may direct a signal to the secondcommunication device 1350 indicating that a connection is requested.Such a signal may result in the second communication device 1350 issuingan alert, such as an audible tone, to notify the receiving party 1390that a call is waiting. Caller identification data associated with theservice center 1360 may also be transmitted to the second communicationdevice 1350. Accordingly, if the second communication device 1350 iscapable of displaying caller identification data, it may display datarelated to the service center 1360. If the second communication device1350 is activated after receiving the signal, such as by the receivingparty 1390 answering a phone call, the telephony switch 1370 may connectthe first communication device 1340 to the second communication 1350device. Upon activation of the second communication device 1350, thetelephony switch 1370 may immediately connect the first and secondcommunication devices 1340 and 1350. Alternatively, the service center1360 or the telephony switch 1370 may prompt the receiving party 1390 toaccept the connection. Then, the call may be connected only if thereceiving party 1390 accepts the connection.

If an approved connection request was received via the first web client124, then the telephony switch 1370 may send signals to both the firstcommunication device 1340 and the second communication device 1350.Caller identification data associated with the service center 1360 maybe transmitted to the first and second communication devices 1340 and1350. Accordingly, if the communication devices 1340 and 1350 arecapable of displaying caller identification data, they may display datarelated to the service center 1360. In response to such signals, thecommunication devices 1340 and 1350 may issue alerts to the calling 1380and receiving parties 1390 of the connection. When the calling andreceiving parties 1380 and 1390 activate the first and secondcommunication devices 1340 and 1350, the two parties 1380 and 1390 maybe connected.

In an exemplary embodiment of the telephony switching system 350, thecaller identification information may include data relating to theservice center 1360, such as a phone number of the service center 1360.In an alternative embodiment, calls may be associated with alternativecaller identification information. For example, and not limitation, thecaller identification information may include an alias, username, orhandle of the other party and/or a telephone number associated with theweb site 305 or service center 1360.

In an exemplary embodiment of the telephony switching system 350, atleast one of the calling party 1380 and the receiving party 1390 (or asponsoring user associated with either) may be required to use creditsto purchase the connection request, the approved connection, or both.Additionally, call crediting may be required for each unit or othermeasurement unit of call time. Credits may be automatically debited fromapplicable accounts when a connection is requested or when a call isconnected.

The cost, in credits, of connection requests and connections may varybased on predetermined variables. For example, connection to a faxmachine may require more credits than connection to a landlinetelephone. A connection during a business day may require more creditsthan a connection on an evening or weekend. When the calling party 1380requests a connection to the receiving party 1390, the calling party'scredit account may be debited for the request. If the receiving party1390 accepts the connection, through contact rules or through anaffirmative approval, credit accounts of both parties 1380 and 1390 maybe debited for the connection. Alternatively, a debit may only berequired for approved connections instead of for connection requests aswell, or a debit may only be required for the calling party 1380.Additionally, in some exemplary embodiments of the telephony switchingsystem 350, a debit may only be required from the calling party 1380when a common user 615 connects to, or requests a connection to, afeatured user 635. Regardless of when the actual debits occur, someexemplary embodiments may substitute a sponsoring user's credit accountinstead of the calling or called party's account, where applicable.

Media Interaction System

The networking system 300 may further comprise a media interactionsystem 360 accessible through the web site 305. The media interactionsystem 360 may enable a first user to interact with a second userthrough a use of one or more media objects.

Media objects may allow users a creative and personal means to interactwith other users. Media objects may comprise various types of media,such as computer animations, other video, audio, or text. Preferably, amedia object may comprise an animation in conjunction with anillustration package capable of superimposing a user's existing displayobjects. An animation in the media object may be implemented in variousformats, such as Flash™, Microsoft Silverlight™, or the like. Whendisplayed, the media object may have a transparent background. In otherwords, media objects of the networking system 300 may appear to float infront of other objects displayed on a client computer 102.

Media objects may comprise web-based objects selectable by the firstuser and sent to the second user after prompting by the first user. Thefirst user may select a media object from a predetermined collection ofmedia objects presented to the first user. The media objects may beassociated with a theme, such as a particular holiday, feeling, orseason. Media objects available for selection on the web site 305 maychange or rotate based on various factors, such as season or politicalclimate.

Media objects may be dynamic and customizable to further personalizeinteractions between the first user and the second user. For example,and not limitation, a username of the first user may be automaticallyinserted into a media object sent to the second user, or the networkingsystem 300 may prompt the first user for text to insert into the mediaobject. For further example, the media object may comprise apersonalized note to the second user. After the first user selects anoption to send the personalized note, the first user may be prompted toenter custom text to be displayed in the note. When the second userreceives the note, an animation may play in the web client 124 of thesecond user. The animation may display, for example, a pen writing thetext entered by the first user.

When a media object is selected for sending, the selected media objectand any user customizations may be stored and queued on the serverassembly 150. To efficiently utilize space on the server assembly 150,if a media object includes an animation, the media object may preferablycomprise no more than approximately 30 seconds of animation at 30 framesper second. Additionally, the file size of a media object is preferablyno more than approximately 150 kilobytes. Those of skill in the art willrecognize that these exemplary animation characteristics and file sizeare provided as sample characteristics for use in an exemplary computersystem. As computing technology improves, these characteristics may bebroadened.

When the first user selects a media object to send to the second user,the chosen media object may be stored in a queue of the server assembly150. In an exemplary embodiment, display of the packaged media object onthe second user's client computer 102 may be purposely delayed until apredetermined event occurs. For example, such display may be delayeduntil the second user returns to a chat room in which the second useractively chats with the first user.

In an exemplary embodiment of the media interaction system 360, themedia object may be delivered to the second user's client computer 102through a pull method. The pull method may be implemented by creating apulse, or heartbeat, that is repetitively fired by the web client 124,and may be received by the server assembly 150. The request may informthe server assembly 150 of a current state of the web client 124 and anyevents that should be handled. In return for each pulse sent by the webclient 124, data is delivered to the web client 124 regarding how tohandle such events.

The first user's request to send the media object may be transmitted tothe server assembly 150 in this manner, and may create an event andaccompanying metadata on the server assembly 150. The server assembly150 may read the metadata to determine how to handle the event. Based onthe metadata, the server assembly 150 may determine that the event is amedia object and should be addressed to the second user's clientcomputer 102. The server assembly 150 may then create an event andmetadata for the second user's web client 124, and may retain the eventand metadata in a queue until the server assembly 150 hears from thesecond user's web client 124. When the second user's web client 124fires a pulse, the server assembly 150 may respond by transmitting thedata in its queue, such as the event related to the media object, to theweb client 124. The web client 124 may then receive the data in thequeue, including the media object event. After the event is received,the second user's web client 124 may display the media object selectedby the first user.

In an alternative exemplary embodiment, in which a communicationschannel is enabled between the second user's web client 124 and theserver assembly 150, the media object may be delivered to the seconduser's client computer 102 via a push method. In that case, the serverassembly 150 may remain aware of the web client 124 because of the openchannel and, therefore, the web client 124 may remain available torespond to requests sent by the server assembly 150. The server assembly150 may send the event and associated metadata directly to the seconduser's web client 124 without the web client 124 firing a pulse todetermine whether it should receive the media object.

The networking system 300 may provide three categories of media objects,including packaged media objects, extended media objects, andbi-directional media objects.

A packaged media object may comprise a flash animation allowing littleto no selectable customization by the first user. In other words, thepackaged media object may be pre-packaged and sent as-is. The packagedmedia object may be an animation, such as a flash animation, which mayinclude a catch phrase or punch line.

A packaged media object may be selected for delivery from variousportions and web pages of the web site 305. Preferably, however, thefirst user may select and send a packaged media object from within achat session with the second user. During the chat session, there may bea portion of the chat web page comprising a menu of sendable packagedmedia objects. The menu may represent each packaged media object as anicon, which may or may not be animated. For example, the web site 305may provide a drop-down menu of selectable media objects. When the firstuser places a cursor over a menu item for a particular packaged mediaobject, a pop-up may identify a name or description of the packagedmedia object.

When the first user clicks a list item representing a chosen packagedmedia object, the packaged media object may be delivered to the seconduser. In some embodiments of the networking system 300, before thepackaged media object is sent, the first user may be asked to confirmthat he wants to send the packaged media object. But this is notrequired. The networking system 300 may display the media object on theclient computers 102 of both the first user and the second user. Forexample, if the media object comprises a flash animation, the flashanimation may be played on each of the client computers 102.

Extended media objects may comprise interactable flash animations fromthe first user to the second user. For example, and not limitation, anextended media object may be a virtual gift, such as a locket containingan image selected by the first user. Alternatively, an extended mediaobject may contain virtual food or a virtual beverage. In an exemplaryembodiment of the networking system 300, the first user may select theextended media object from a virtual gift shop on the web site 305. Theextended media object may then be displayed to the second user withoutaffirmative prompting of the second user or, alternatively, the extendedmedia object may be delivered to a virtual mail box or other virtuallocation of the second user. In the latter case, the second user may berequired to retrieve the extended media object from its virtuallocation.

A difference between a packaged media object and an extended mediaobject may be that, before a chosen extended media object is sent, thefirst user may be prompted to provide some degree of customization forthe extended media object. For example, the first user may be asked toselect a specific gift or beverage for the second user. As a result,unlike with a packaged media object, the first user may observe adifferent display of the media object than observed by the second user.For example, while the first user may view a virtual bar for selecting adrink to send the second user, the second user may view a prepareddrink.

A bi-directional media object may allow, or require, interaction fromboth the first user and the second user. For example, and notlimitation, the bi-directional media object may comprise a game for twoor more players. The first user may initiate the bi-directional mediaobject from, for example, a profile of the second user. Alternatively,the first user may choose to send a bi-directional media object and maythen be prompted to select a recipient user, such as the second user, toreceive the bi-directional media object. After the first user initiatesthe bi-directional media object, a prompt or invitation may be sent tothe second user, requesting that the second user participate in thebi-directional media object.

During interaction within a bi-directional media object, the first usermay dictate an action and may receive a response from the second user.This may occur iteratively in a bi-directional media object constitutingan ongoing game. Selected action of the first and second users within abi-directional media object may be stored in a shared object within aflash animation file.

Two or more users may participate in a bi-directional media object. Whenusers, such as the first and second users, participate in abi-directional media object, their web clients 124 may become staticallylinked through a dedicated server object providing a dedicatedcommunications channel. This may provide an efficient delivery mechanismfor the users.

The media object may be cached on the client computers 102 of the firstand second users. In a first exemplary embodiment of the mediainteraction system 360, an HTTP protocol is provided for implementing apull method for bi-directional media objects. The pull method may besimilar to that described above for other media objects. With thebi-directional media object, however, the pulse from each involved webclient 124 requests that the server assembly 150 act as a proxy, andthat the data being transmitted from the web client 124 should beaddressed to the dedicated server object associated with thebi-directional media object. In the pulse, the web client 124 may alsorequest that the server assembly 150 transmit event data relating to thebi-directional media object, such as actions of other usersparticipating in the bi-directional media object.

In another exemplary embodiment, when a communications channel isenabled between the web client 124 and the server assembly 150, a pushmethod may be implemented similar to the push method described above. Inthat case, the web client 124 may have direct access to the dedicatedserver object, which may send events and metadata for the bi-directionalmedia object directly to the involved web clients 124.

Because the bi-directional media object may require interaction fromboth the first and second users, it may be required that both users belogged into the web site 305 during use of the bi-directional mediaobject.

When a bi-directional media object is complete, such as when a game hascome to its conclusion, either of the users may choose to run thebi-directional media object again. In that case, the other user mayreceive a prompt requesting whether to replay the bi-directional mediaobject. If the user and the second user agree to replay thebi-directional media object, the bi-directional media object may berestarted. Results of the bi-directional media object, such as who won agame in the bi-directional media object and statistics of the game, maybe stored in a database on the server assembly 150 for future use.

FIG. 15 illustrates a flow diagram of an operation 1500 of abi-directional media object, according to an exemplary embodiment of themedia interaction system 360. At 1501, a web client 124 may begin toplay the bi-directional media object. At 1505 and 1510, the first usermay send a request to the second user requesting participation in thebi-directional media object. At 1515, the second user may agree orrefuse to participate. If the second user refuses, a rejection may bedisplayed to the first user at 1545, and the bi-directional media objectmay terminate at 1550. Otherwise, if the second user agrees toparticipate, the bi-directional media object may be displayed on the webclients 124 of both users at 1520. At 1525, a cycle may begin of thefirst and second users taking turns interacting with the bi-directionalmedia object. In a first iteration of the cycle, the first user mayinteract with the bi-directional media object at 1525. Interaction datamay be transmitted to the server assembly 150 at 1530, and may betransmitted to the second user at 1535. At 1540, the results of thefirst user's interaction may be displayed on the web clients 124 of thefirst and second users. Then, the cycle may repeat at 1525, with thesecond user interacting with the bi-directional media object.

Accordingly, the media interaction system 360 may enable users tointeract with one another through multimedia content displayed on theweb site 305.

Display System

The display system 370 of the web site 305 may provide a means to modifya look and feel of the web site 305 as presented to the user via the webclient 124. Predetermined elements of the visual look and data contentof the web site 305 may be user-adjustable. The data presented to theuser may be customized by changing the colors and layout of web sitedata element containers. Also, the web site data presented may befiltered by the user's theme preference.

User configurations may be stored in a web cookie on the client computer102, and in a database field unique to each individual user's profile.Web cookies provide a standard means for the web client 124 to maintainits state within a given internet domain. Accordingly, future visits tothe web site 305 may not require the web client 124 to download datarelating to the theme, color, or display defaults for the user. The webcookie may remain on the client computer 102 even after the web client124 is closed. If the user logs into the web site 305 and the web client124 is unable to find a web cookie on the client computer 102, the webclient 124 may then retrieve default theme, color, and display value,and may create a web cookie for future use.

When the user logs onto the web site 305, an access token is generatedfor the user. A new access token may be generated each time a user isauthenticated and logs into the web site 305. The access may be providedto the server assembly 150 when the web client 124 interacts with theserver assembly 150. The access token may enable the server assembly 150to uniquely identify the web client 124. The access token may have alimited lifespan and may be regenerated at each login. The access tokenmay be stored in web cookies and in a cache object. While the user islogged into the web site 305, the user's configurations may be stored inthe cache object in addition to being stored in the database.

If the user has not selected a preferred theme or color in their website preferences, a default theme and color may be used. Defaultconfigurations may be based on certain data relating to the user. Suchdata determining the default configuration may include, withoutlimitation, the user's member category (i.e., common or featured),gender, or specified purpose for using the web site 305. The web sitemanager 308 may modify available themes and color schemes periodically,or at any time. Users may be able to change a displayed color schemewith a single mouse click. This may be made possible by switchingcascading style sheets (“CSS”) and page graphics of the web site 305through an object-oriented language and dynamic updates.

Page graphics and text may be altered for a variety of needs. Suchalteration may be implemented by using compartmentalization, or ahierarchy, for art and text for presentation to the user via the webclient 124. For example, distinct folders may be provided for site,theme, and sub-theme. Each folder may include, for example, a color anda language. Further, each color for site, theme, and sub-theme mayinclude its own language folder.

By breaking the site into these compartments, a change of folderreference for each CSS, graphic, or text object may dynamically changecolors, themes, and languages without requiring reloading of a web pageon the web site 305. This implementation may also simplify developmentof the web site 305, as background code need not define themes,sub-themes, languages, or colors. New themes, colors, languages, andvarious other configuration details may be provided without anyadditional code.

When the user changes his or her color preference, the change is storedin the current session's cache object and in the user's local webcookie. The user's login session on the web site 305 may expire from thecache object after the web site 305 is unloaded from the web client 124.Removal of the cache object on the server assembly 150 may occur byvarious means. In an exemplary embodiment of the display system 370, theweb client 124 may send a log-off request to the server assembly 150. Inthe event this signal is not received, the server assembly 150 mayrecognize that the web client's pulse has terminated. Then, the serverassembly 150 may retain the cache object for a predetermined duration,or until occurrence of a predetermined event, before removing the cacheobject. Retaining the cache object for a predetermined duration, oruntil occurrence of a predetermined event, may ensure that the serverassembly 150 does not prematurely remove the cache object.

At a color change request, various tasks may be performed to effect anew color scheme. The user's cache object may modify a stored colorvalue. The user's web site cookie may be altered with the new colorvalue. The user's web site preferences database field may be updatedwith the new color value. The CSS provided for web site 305 renderingmay change to a CSS specific to the new color value. Additionally, theweb site 305 may be re-rendered using the new web site preference color.

As described above, color changes may be implemented through foldercompartmentalization. Folders may be provided for each color option ofthe web site 305. Accordingly, the web client 124 may dynamically altera color of the web site 305 without requiring a re-login or reloading ofa web page of the web site 305.

Themes may be provided to allow the user to further customize the website 305. A theme may define graphic images and data content presentedto the user. In addition to being stored in the user's database field,the chosen theme may also be stored in the cache object when the user islogged into the web site 305.

When the user selects an available theme, a dynamic update may instructthe application code to display an appropriate set of data and graphicsapplicable to the theme. The theme choice may be implemented through anobject-oriented programming language, and may be processed on thepre-render of page elements.

Photo Management System

As mentioned above, the networking system 300 may further include aphoto management system 380. The photo management system 380 may enableviewing, organizing, and editing images associated with a user account.Such images may include, but are not limited to, photographs andgraphical representations of objects.

With the photo management system 380, a user may have an image libraryon the web site 305, and may utilize an image editor on the web site 305to modify images in the image library. A user may be able to view photolibraries, or predetermined portions of photo libraries, of other users.The user may upload images to the library, and may also create andmodify images in the library. From the image library, the user may sortimages and arrange images in folders for more efficient organization.

The photo management system 380 may include a gallery for viewing imagesin the image library. In the gallery, the user may scroll through allimages, or a set of images, in the image library.

To enable uploading of images, a photo upload dialog may be provided ona web page of the photo management system 380. Through the photo uploaddialog, the user may browse images on, or linked to, the client computer102 and may choose one or more of such photos to add to the imagelibrary. A browser of the photo upload dialog may enable users to viewthumbnails of images on the client computer 102. This may enable theuser to more efficiently select images that the user intends to add tothe image library.

Uploaded or newly created images in the image library may not beimmediately viewable by other users. When uploaded or created, a newimage may have an unapproved status. While approved images may beviewable by others, unapproved images may not be viewable by otherusers. For an image status to change from unapproved to approved, theweb site manager 308 may be required to approve the image. Additionally,an image may not be viewable if it has not been selected as a viewableimage by the user of the image.

The photo management system 380 may require that no more than apredetermined number of images from the user's image library beappointed for each purpose that may be given to images. For example, andnot limitation, the user may be required to select no more than apredetermined number of images viewable by other users, or no more thana predetermined number of images viewable by those other userscategorized as “friends” of the user. The user may appoint an image to acertain purpose by dragging the image into a designated section of a webpage of the photo management system 380.

FIG. 16 illustrates a flow diagram of a process 1600 of managing andediting images in an exemplary photo management system 380. At 1601 and1602, the web client 124 may communicate with a database on the serverassembly 150. At 1604 and 1608, the web client 124 may receive imagedata from the database. The web client 124 may then load images from theimage library at 1610. At 1612, the web client 124 may assign the imagesaccording to their appointments, such as assigning a position of animage in a certain location based on whether the image represents partof the user's viewable profile, or whether the image is viewable only tofriends. The web client 124 may display a graphical user interface tothe user at 1614.

The user may then have an ability to perform actions regarding theimages, as described above. At 1616, the user may modify appointments ofvarious images. At 1618, the user may flip an image. At 1620, the usermay rotate an image. At 1622, the user may delete an image from theimage library. At 1624, the user may assign an image to a particularappointment. After the user selects any one of the above actions, datamay be communicated between the client computer 102 and the serverassembly 150 to accomplish the selected task, and to store the user'smodifications to images on the database of the server assembly 150. Ifthe selected action was successful at 1628, the web site 305 may notifythe user of the success at 1630. Alternatively, if the action failed at1632, the user may be notified of the failure at 1634.

The user may upload images to the image library at 1636. In an exemplaryembodiment of the photo management system 380, a file browser may bedisplayed at 1638 to assist the user in selecting a file to be uploaded.At 1640, the selected file may be prepared for uploading, and at 1642,image data from the selected file may be transmitted from the clientcomputer 102 to the server assembly 150. If this operation is successfulat 1644, a confirmation may be displayed to the user at 1646. Also at1646, the web client 124 may refresh a web page of the image library todisplay the image library containing an image from the selected file.The process 1600 may then, once again, load images in the image libraryat 1610. Alternatively, if the operation of uploading the selected imagefile fails at 1648, an error message may be displayed to the user at1650.

The image editor of the photo management system 380 may enable the userto modify images in the image library. The image editor may includetools to crop an image, rotate an image, flip an image, delete an image,create a photo profile, and various other image-editing tools.

Additionally, the photo editor may provide a tool enabling the user tocreate a thumbnail image, which may represent the user on the web site305. The user may associate the thumbnail image with text, which may beused in conjunction with the thumbnail to represent the user on the website 305. Preferably, the user may have only a single thumbnail image,so creating a new thumbnail may automatically delete any old thumbnail.

The thumbnail tool may enable the user to crop an image to a specifiedsize or to specified dimensions or aspect ratio. To use the thumbnailphoto, the user may first select an image from the image library. Theuser may select a first point on the selected image, and may do so byclicking with a mouse button, with a cursor over the first point, andholding the mouse button down. The user may then select a second pointon the selected image. Selecting the second point may entail draggingthe cursor to the second point while holding the mouse button down, andthen releasing the mouse button with the cursor over the second point.As the first user drags the cursor between the first and second points,a rectangle may be displayed between the first and second point, suchthat the first and second points lie on opposite corners of therectangle. If valid, a portion of the selected image lying inside therectangle may represent a new thumbnail created by the user. Theselected portion may be deemed invalid, however, if, for example, therectangle extends outside the bounds of the image. If the selectedportion is invalid, a new thumbnail may not be created for the user.

FIG. 17 illustrates a process 1700 of editing images with an exemplaryimage editor of the photo management system 380. After the networkingsystem 300 displays the graphical user interface at 1614 (as describedin FIG. 16), the user may edit images as described above. For example,the user may perform any of the following: flip an image at 1756, rotatean image at 1758, delete an image at 1760, and create a thumbnail at1766. At 1726, data regarding the user's image modifications may becommunicated between the client computer 102 and the server assembly150. If the modifications fail at 1732, the user may be informed of thefailure at 1734. On the other hand, if the modifications succeed at1728, the user may be informed of the success at 1730.

At 1762, the user may attempt to crop an image. At 1764 and 1768, theuser may select a portion of the image as described above, with respectto creating a thumbnail. At 1770, the networking system 300 maydetermine whether the selected portion of the image is valid. At 1772,the user may be informed of success or failure of cropping the imagebased on the user's selection. If the cropping was successful, data maybe sent to the server assembly 150 to store the user's modifications tothe image at 1774.

The networking system 300 may store both an original raw image and a setof attributes representing modification to the image. The modificationsmay be a result of photo editing on the part of the user. The attributesmay contain all data required to reconstitute the current image havingthe user's previous modifications. Accordingly, when an image is to bedisplayed on the client computer 102, the raw image may be manipulatedwith the stored attributes before being delivered to the client computer102. FIG. 18 illustrates a flow diagram of an exemplary process 1800 ofdelivering images to the client computer 102 in the photo managementsystem 380.

As shown in FIG. 18, at 1818, the networking system 300 determineswhether the user has requested a rotation of the image. Suchdetermination may occur by examining the stored attributes associatedwith the image. If a rotation is requested, at 1824, the desiredrotation is performed. At 1826, the networking system 300 may determinewhether the image should be flipped. At 1834, the networking system 300may determine whether to perform red-eye reduction and, at 1836, whethersuch red-eye reduction is to be performed manually or automatically. Thenetworking system 300 may then use the attributes to re-perform thered-eye reduction as originally performed. If a manual red-eye reductionwas performed, characteristics of such reduction may be retrievable fromthe stored attributes.

At 1842, the networking system 300 may determine whether color levelsshould be modified. If so, at 1844, the networking system 300 maydetermine whether the user desired manual or automatic modification ofcolor levels. At 1850, the networking system 300 may determine whetherto modify brightness and contrast of the image and, at 1852, whethersuch modifications are manual or automatic. At 1854 and 1856, thenetworking system 300 may perform the requested modifications. Finally,at 1858 the resulting image is returned.

The image may be at least partially defined by image manipulationarguments, which may reflect the user's modifications to the image. Theserver assembly 150 may store each image as well as one or more sets ofimage manipulation arguments. The image manipulation arguments may bestored in a table or array along with a reference to the associatedimage. Each set of manipulation arguments for the image may define adisplayable image created through a set of user manipulations to theoriginal image. For example, a user may create a thumbnail from theoriginal image to identify the user on the web site 305. The user mayalso rotate and crop the original image for display in the user'sprofile. Depending on whether the web site 305 is displaying thethumbnail version of the image or the profile version of the image, thenetworking system 300 may apply a different set of manipulationarguments to the image when displaying the image on the web site 305.

Preferably, the image manipulation arguments define modifications to theimage in a coordinate system of the image. For example, if the userrotates and then crops the image, both operations may be stored in a setof image manipulation arguments with reference to coordinates relativeto one or more points on the image. This enables appearance of the imageto be independent of an order in which the rotation and cropping areapplied to the image before the image is displayed. If, in contrast,operations are stored with reference to an absolute coordinate system,then reconstituting the modified image would require performing theoperations in the order in which the user originally performed suchoperations. The present photo management system 380 may allow moreflexibility by enabling operations within a set of manipulationarguments to be stored in various orders.

A second set of arguments, display arguments, associated with an imagemay be provided to define how the web client 124 may manipulateformatting and display of the image. For example, although the image maybe stored in a size of 800×600 pixels, the web client 124 may displaythe image into a 320×200 display area. Accordingly, display argumentsmay instruct the web client 124 to shrink the image to fit in a 320×200display area.

FIG. 19 illustrates a flow diagram of a process 1900 of displaying animage in the photo management system 380. At 1901, the user may requestthat an image be displayed. Accordingly, the networking system 300 mayretrieve the image from storage on the server assembly 150 at 1902 and1904. At 1906, the networking system 300 may determine whether there areany display arguments for the image. At 1908, the networking system 300may determine that display arguments should be applied to the image, andsuch arguments are applied at 1910. After the display arguments havebeen applied, or after the networking system 300 determines that displayarguments need not be applied, at 1912, the networking system 300 maydetermine whether the user requested any user manipulation arguments forthe image. If user manipulation arguments exist for the image, thenetworking system 300 may manipulate the image according to the usermanipulation arguments beginning at 1810 (FIG. 18). Finally, at 1914,the image may be displayed to the user.

Image caching may be provided in the photo management system 380 of thenetworking system 300. Caching may result in efficient image loading,while maintaining conventional benefits of retaining stored images onthe database, such as reliable long-term storage. When a web client 124requests an image from the networking system 300, the image may bemodified by parameters of the stored attributes before the image isdelivered to the web client 124 at the client computer 102. Images aremodified by the processing server using a series of parameters providedwhen a request is made. After all modifications are complete, the imagesmay be saved to a cache server, which may comprise a storage deviceassociated with a server in the server assembly 150. Use of the cacheserver to store the modified image may reduce or eliminate the need forthe server assembly 150 to repetitively process the image beforedisplaying it. Data in the cache server may be disposable and,accordingly, may be removed from the cache server when the user logs outor when space is needed. The storage device may be implemented in aRedundant Array of Inexpensive Disks (“RAID”) array to enhance speed,capacity, and performance of the storage device.

Image caching may relieve the server assembly 150 of potentiallyextensive processing of the image, by writing the image to the storagedevice after the image has been modified according to its associatedstored attributes. If the image is requested again, the networkingsystem 300 may retrieve a cached copy of the image from the storagedevice instead of from a database on the server assembly 150.

A benefit of image caching is stateless replication, which enables newservers to be added to the server assembly 150 without replicating anexisting cache. Conventionally, each server would be required toreplicate caches of other servers, and to synchronize its cache withother servers. This utilizes time and bandwidth. In exemplaryembodiments of the photo management system 380, however, a newly-addedserver would not be required to synchronize cached images with otherservers of the server assembly 150. If a requested image does not existon a storage device of the new server, the image may be retrieved fromthe database, modified, and then cached on the new server. Accordingly,the caching of a particular image need not occur until that image isneeded by the new server.

Messaging System

As mentioned above, the networking system 300 may further comprise amessaging system 390. The messaging system 390 may enable a first userto leave a message for a second user of the networking system 300. Forexample, the messaging system 390 may enable a common user 615 to leavea message for a featured user 635, such that the featured user 635 mayview and respond to the message at the convenience of the featured user635. A featured user 635 may also leave a message for a common user 615.Additionally, a common user 615 may leave a message for another commonuser 615, and a featured user 635 may leave a message for anotherfeatured user 635.

FIG. 20 illustrates an exemplary web page of the messaging system 390.As shown in FIG. 20, the messaging system 390 may comprise a messagearea 2010, at least one graphical tool 2020, and a color selector 2030.

The message area 2010 may provide a background for the message. In someexemplary embodiments of the messaging system 390, the message area 2010may look similar to a whiteboard, blackboard, piece of paper, computermonitor, or various other objects on which one might conventionallyleave a message or receive a message. The look and feel of the messagearea 2010 may be customizable. For example, and not limitation, thefirst user may change an appearance of the background provided by themessage area 2010 by clicking a button labeled “Background” on the webpage.

In an exemplary embodiment of the messaging system 390, the message area2010 of a particular user may retain text and images left by previoususers of the same message area 2010. Accordingly, when the first userviews the web page displaying the second user's message area 2010, thefirst user may see messages previously left by the first user and byother users.

The graphical tools 2020 may comprise one or more representations ofimplements for creating the message. For example, a stylus 2022 and aneraser 2024 may be provided as graphical tools 2020. Other graphicaltools 2020 provided may include, without limitation, a text tool, abrush tool, a spray paint tool, a straight line tool, a rectangle tool,and a circle tool. When activated, the stylus 2022 may add portions of amessage to the message area 2010, while the eraser 2024 may removeportions of a message from the message area 2010.

Characteristics of the graphical tools 2020 may be customizable. Forexample, a size and shape of a graphical tool 2020 may be customizable,which may result in a customizable size and shape of modificationsresulting from use of the graphical tool 2020. For example, increasingthe size of the stylus 2022 may increase a width of a line drawn in themessage area 2010 with the stylus 2022. Additionally, transparency of agraphical tool 2020 may be customizable, such that a resultingmodification to the message area 2010 may become more or less opaque.Customizations may affect a single graphical tool 2020 or,alternatively, all graphical tools 2020, depending on either userpreference or a specific embodiment of the messaging system 390.

The color selector 2030 may present the first user with two or morecolor blocks 2035 containing colors applicable to one or more graphicaltools 2020. Each color block 2035 may be a predetermined color. When thefirst user selects a color block 2035, the color of the color block 2035may be applied to the graphical tool 2020 next utilized in the messagearea 2010. A default color may be provided if the first user does notselect a color block 2035. For example, a black color may be applied tographical tools 2020 when the first user does not select a color block2035.

Additionally, the color selector 2030 may allow the first user to adjustcharacteristics of a color, such as hue and saturation, and therebycreate a custom color for application to a graphical tool 2020.

A message of the messaging system 390 may be created by manipulating agraphical tool 2020 on or in proximity to the message area 2010. Thefirst user may select a graphical tool 2020 and, optionally, a color.When the first user activates the graphical tool 2020, such as byclicking a mouse button, the graphical tool 2020 may be applied to themessage area 2010, thereby modifying a visual appearance of the messagearea 2010. For example, when the stylus 2022 is activated, moving thestylus 2022 across the message area 2010 may result in a line beingdrawn along a path of the stylus 2022 in the message area 2010. Forfurther example, when the eraser 2024 moves across the message area2010, text and images in a path of the eraser 2024 may be removed fromthe message area 2010. The modified visual appearance of the messagearea 2010 represents a viewable message. The message may comprisevarious combinations of text and images in the message area 2010, andmay or may not be intended to portray a specific idea to a recipient ofthe message.

During message creation, the first user may be able to save the message.This may be enabled, for example, through use of a web page button orlink labeled “Save.”

Further, the first user may be able to undo a previous action. This maybe enabled, for example, through use of a button or link labeled “Undo.”In some exemplary embodiments of the messaging system 390, an action maynot be undone if the action preceded a saving of the message, asdescribed above.

FIG. 21 illustrates a flow diagram of an exemplary process 2100 ofleaving a message, such as a text comment, through the messaging system390. As shown in FIG. 21, three layers of operation may be implementedin the messaging system 390. These operational layers may include a userinterface layer 2102, an application layer 2104, and a database layer2106. Steps of the process 2100 occurring in the user interface layer2102 may describe an interaction of the messaging system 390 with theuser. Steps of the process 2100 occurring in the application layer 2104may represent operations that occur in the client computer 102. Finally,steps in the database layer 2106 may occur in a database on the serverassembly 150.

At 2110, the first user may enter a text comment for the second user.This may occur through use of the stylus 2022. After such text isproduced, the text is stored as a record in a database on the serverassembly 150 at 2120. Accordingly, at 2130, the text may be retained ina table of the database and properly associated with a message area 2010of the second user. At 2140, the new text comment may be rendered.Rendering may generally take place behind the scenes of the web page,and a rendered image may not be viewable until displayed on the webpage. At 2150, the new text comment may be displayed in the message area2010, which may occur by making viewable a rendered image of the textcomment.

FIG. 22 illustrates a flow diagram of an exemplary operation 2200 ofretrieving a message, such as a text comment, from the messaging system390. As in FIG. 21, three layers of operation 2102, 2104, and 2106 maybe utilized in retrieving a message. At 2210, the first user may requestthat a text comment be displayed. Such a request may be implied when thefirst user navigates to a web page displaying the message area 2010. Therequest may be transmitted through the messaging system application, at2220, to the database. At 2230, the text comment may be retrieved fromthe database. The messaging system 390 may then render the text comment,preferably in HTML format, at 2240. Finally, at 2250, the text commentmay be displayed to the first user.

FIG. 23 illustrates a flow diagram of an exemplary general operation2300 of the messaging system 390. At 2301 and 2302, the web client 124may communicate with a database on the server assembly 150 regardingmessage data. At 2304 and 2307, the web client 124 may receive messagedata from the database. The web client 124 may then display thegraphical user interface (“GUI”), including the message area 2010, viathe web client 124 to display messages to a user. At 2310, the messagingsystem 390 may determine whether the user is attempting to leave acomment in the message area 2010. If so, the user's comment is acceptedat 2312. Otherwise, an empty comment is accepted at 2313.

At 2314, a record may be created in the database for storing thecomment. At 2316 and 2326, the web client 124 and the server assembly150 may communicate with each other. The web client 124 informs theserver assembly 150 of modifications to the message area 2010, so thatthe database on the server assembly 150 may be updated. The serverassembly 150 may then send a confirmation to the web client 124. At2318, the GUI may be update to display the new comment to the user.

Operations similar to those of the image editor of the photo managementsystem 380 may also be integrated into the messaging system 390. Forexample, and not limitation, at 2322, the user may select a tool tomodify the GUI. Specifically, the user may modify the message area 2010by leaving a message. After a modification, the GUI may be updated todisplay the modifications to the user.

If the user indicates that he would like to save his modifications tothe message area 2010, the messaging system 390 may receive a command tothe save at 2320. The web site 305 may prompt the user for confirmationat 2321. If the user confirms his desire to save, an image of themessage area 2010 may be sent to the server assembly 150 at 2324. At2326, the database on the server assembly 150 may be updated with theuser's modifications. Hence, the user may leave a message in the messagearea 2010, and may save his message for later viewing. After thedatabase is updated, the message application 2104 may close at 2328.

Accordingly, through implementation of the crediting system 310, thechat bidding system 330, the performance bidding system 340, thetelephony switching system 350, the media interaction system 360, thedisplay system 370, the photo management system 380, and the messagingsystem 390, the networking system 300 may enable interaction betweenusers.

While the networking system 300 has been disclosed in exemplary forms,it will be apparent to those skilled in the art that many modifications,additions, and deletions may be made without departing from the spiritand scope of the system, method, and their equivalents, as set forth inthe following claims.

1. A networking method comprising: providing a plurality of common useraccounts, each common user account comprising a common profile having acommon set of privileges; providing a plurality of featured useraccounts, including a first featured user account comprising a featuredprofile associated with a featured set of privileges and an alternativeprofile associated with a common set of privileges; receiving a requestfrom the first user account to appear as a common user account;automatically activating the alternative profile and assigning theassociated common privileges to the first featured account in responseto the request; and automatically deactivating the featured profile inresponse to the request, wherein no more than one of the featuredprofile and the alternative profile are active while the first featureduser account is active.
 2. The networking method of claim 1, furthercomprising: executing an activity having a common user role and afeatured user rule; placing a common user associated with the commonuser account in the common user role of the activity; and placing afeatured user associated with the first featured user account in thecommon role of the activity, when the alternative profile of the firstfeatured user account is active.
 3. The networking method of claim 2,further comprising placing the featured user associated with the firstfeatured user account in the featured role of the activity, when thefeatured profile of the first featured user account is active.
 4. Thenetworking method of claim 1, further comprising: displaying arepresentation of a first common user account, from among the pluralityof common user accounts, the representation of the first common useraccount comprising a first characteristic identifying the first commonuser account as belonging to a common user; and displaying arepresentation of the first featured user account, wherein therepresentation of the first featured user account comprises the firstcharacteristic identifying the first featured user account as belongingto a common user when the alternative profile of the first featured useraccount is active.
 5. The networking method of claim 4, wherein therepresentation of the first featured user account comprises a secondcharacteristic identifying the first featured user account as belongingto a featured user, when the featured profile of the first featured useraccount is active.
 6. The networking method of claim 5, furthercomprising dynamically updating the representation of the first featureduser account based on whether a currently active profile of the firstfeatured user account is the featured profile or the alternativeprofile.
 7. The networking method of claim 5, the featured user accountbeing configured to conceal featured status by activating thealternative profile.
 8. The networking method of claim 1, furthercomprising: associating a first credit account with a first useraccount; determining that the first credit account is at or below apredetermined threshold; and automatically classifying the first useraccount as having a sponsored status in response to the first creditaccount being at or below the predetermined threshold.
 9. The networkingmethod of claim 8, further comprising: receiving a request for asponsoring user account to sponsor the first user account, thesponsoring user account being associated with a second credit account;receiving a request for the first user account to participate in apurchasable activity, the purchasable activity being associated with anon-zero cost; and automatically debiting the second credit account forthe non-zero cost of the purchasable activity to pay for participationin the purchasable activity by the first user account.
 10. Thenetworking method of claim 8, further comprising removing the sponsoredstatus from the first user account when the first credit account meetsor exceeds the predetermined threshold.
 11. A networking systemcomprising: a plurality of common user accounts associated with aplurality of common users, each common user account being associatedwith a corresponding common user, and each common user accountcomprising: a common profile comprising a first characteristicidentifying the common profile as belonging to one of the common users;and a plurality of featured user accounts associated with a plurality offeatured users, each featured user account being associated with acorresponding featured user, and each featured user account comprising:a featured profile comprising a second characteristic identifying thefeatured profile as belonging to one of the featured users; and analternative profile comprising the first characteristic identifying thefeatured profile as belonging to one of the common users; wherein nomore than one of the featured profile and the alternative profile isactive at a given moment; wherein each featured user account isconfigured to appear as a common user account when its respectivealternative profile is active.
 12. The networking system of claim 11,the featured profile of a first featured user account comprising a firstdata set, and the alternative profile of the first features usercomprising a second data set, wherein activities performed through thefirst featured user account modify the first data set when the featuredprofile is active and modify the second data set when the alternativeprofile is active.
 13. The networking system of claim 11, the featuredprofile of a first featured user comprising a first data set related tothe first featured user, the alternative profile of the first featuresuser comprising a second data set related to the first featured user,wherein the first data set is hidden when the alternative profile of thefirst featured user is active.
 14. The networking system of claim 11,further comprising: a first representation of a first common useraccount, from among the plurality of common user accounts, the firstrepresentation being identifiable as having a non-featured status; and asecond representation of a first featured user account, from among theplurality of featured user accounts, the second representation beingidentifiable as having the non-featured status when the alternativeprofile of the first featured user account is active.
 15. The networkingsystem of claim 14, the second representation being dynamically updatedto indicate a featured status when the featured profile of the firstfeatured user account becomes active.
 16. The networking system of claim14, further comprising: a common representation template customizable bya current user, wherein the first representation of the first commonuser account is based on the common representation template; and afeatured representation template customizable by the current user andapplicable to the plurality of featured user account; wherein the secondrepresentation of the first featured user account is based on the commonrepresentation template when the alternative profile of the firstfeatured user account is active.
 17. The networking system of claim 16,the second representation being dynamically modified to be based on thefeatured representation template when the featured profile of the firstuser account becomes active.
 18. A computer program product embodied ina computer-readable medium, the computer program product adapted toeffectuate a networking method, the method comprising: providing anactivity having a common user role and a featured user role; providing afeatured user account having a featured profile and an alternativeprofile, wherein no more than one of the featured profile and thealternative profile is active while the featured user account is active;executing the activity with a common user associated with the commonuser account performing in the common user role; executing the activitywith a featured user associated with the featured user accountperforming in the featured user role, if the featured profile is active,and with the featured user associated with the featured accountperforming in the common user role, if the alternative profile isactive; and switching an active profile of the featured user accountbetween the featured profile and the alternative profile on demand. 19.The computer program product of claim 18, the networking method furthercomprising representing the featured user account as having anon-featured status when the alternative profile is active.
 20. Thecomputer program product of claim 19, the networking method furthercomprising representing the featured user account as having a featuredstatus when the featured profile is active.
 21. A computer programproduct embodied in a computer readable medium wherein the computerprogram product comprises an algorithm adapted to effectuate anetworking method, the method comprising: providing a plurality of useraccounts, including a first user account associated with a first user;associating a first credit account with the first user account;detecting that a balance of the first credit account is at or below apredetermined threshold; automatically applying a sponsored status tothe first user account in response to the first credit account being ator below the predetermined threshold; providing a plurality of featureduser accounts; receiving a request for the first user to participate inan activity with one or more of the featured user accounts; andautomatically debiting a second credit account associated with a seconduser in response to the request to participate, if the first useraccount has the sponsored status.
 22. The computer program product ofclaim 21, the networking method further comprising: displaying arepresentation of the first user account while the balance of the firstcredit account is at or above the predetermined threshold; anddynamically updating the representation of the first user account toindicate the sponsored status, after the sponsored status is applied tothe first user account.